News for hackers. Stuff that matters.
Re:How does Monzo keep 1,600 microservices spinning? Go, cle... by kitd on Monday March 30, 2020 @06:06AM (#22726601)
Who at Monzo could possibly understand how a significant portion of their platform works, in detail, and be confident that knowledge isn't going to be outdated in ten minutes from now? Who understands how changes to each of these tiny pieces will impact the others?

Tbf, this can apply to any sufficiently complex system, whether or not it uses microservices.

It's why interfaces are so damned important, especially communicating them with stakeholders. Done properly, you only need to focus on the bits of a system that matter to you. At least microservices get to use OpenAPI.

Re:How does Monzo keep 1,600 microservices spinning? Go, cle... by discreteevent on Monday March 30, 2020 @06:16AM (#22726646)
There's a major difference between 600 components that follow the fallacies of network computing and 600 that don't.
Re:How does Monzo keep 1,600 microservices spinning? Go, cle... by kitd on Monday March 30, 2020 @11:26AM (#22728745)
Agree completely, but that wasn't the point I was replying to, which was about totally understanding your system.

Don't worry. I've suffered (and still do) as much as anyone working with microservices, trying to reconcile and decipher logs.

But total knowledge is rarely possible in a large system. At least microservices acknowledges this. If anything, they can help by following Conway's Law.