Have you ever been in a situation where your assumptions were challenged, and you realized you were wrong? Can you tell us about it?

Question

Anonymous · Accepted Answer

Decided to move to several microservices architecture at some point, to meet
upcoming growth challenges, but the parts with highest load left in monolith,
and new integrations didn't give enough load to justify the switch.

In short, we've already had Amazon, eBay, Walmart integrations and a lot of
customers with big usage of them, and constant flow of new minor features for
these integrations. So in order to better manage load and development, I decided
to make new marketplace integrations like Etsy, BackMarket, NewEgg, Tiktok shop,
on the separate microservices.

But that didn't give us desired outsome because development, and computing load
was 10 times lower on these integrations. Correct approach would be to pull
these existing integrations (Amazon, eBay, Walmart) into separate microservices
out of monolith

Anonymous · Answer

I recently took over a team from a different tribe, my approach was to observe
what the team was doing and how I could best help them.

One of the observations was that a team member was not contributing as much as
was expected and ultimately was underperforming. I raised this with the previous
line manager and he validated my concerns and said that he will likely get
another developing in performance review and be put on a PIP.

After some initial conversation with the individual, discussing what I've
observed and how his not meeting expectations, I was pretty sure, this person
was checked out and was likely heading for a difficult performance review

However, after some further discussion and people a relationship with that
individual, they opened up and start to share their difficulties they were
having. This then allowed me reach out the necessary teams to get them the
support they needed.

Utlimately, they proved me wrong, as due the the hard work with both put in, his
on track for a good performance review

I

Anonymous · Answer

Pushed for single tenancy of application because of monolith and legacy
architecture but had to move to multi tenancy later on because of scalability
issues.

Have you ever been in a situation where your assumptions were challenged, and you realized you were wrong? Can you tell us about it?

Practice this question with AI

Go Premium

Community Answers

Unlock Full Access

Unlock Full Access

Unlock Full Access

Practice More Questions