[woutr_be]

> By modularizing our front and back ends in such a way, no one person is responsible for keeping an entire app in their head all the time. As developers, it’s important to have a strong sense of our broader architectural ecosystems

Maybe I’m misinterpreting this, but those two sentences contradict themselves in my opinion.

Now either developers need to fully understand all the different micro-services, and understand how they all work together. Or developers will lose sight of the bigger architecture and end up specialising in only a few services.

But more importantly, I doubt micro-services will solve their problem of their monolith not being modular. That seems like an architectural problem that can also be solved in a monolith.

But in general, I have never seen a company that switched to micro-services, and didn’t end up regretting it a few years later.

[tutfbhuf]

> Or developers will lose sight of the bigger architecture and end up specialising in only a few services.

This is unavoidable for many companies, since the code bases are far to large for any single person to grasp them all.

> But more importantly, I doubt micro-services will solve their problem of their monolith not being modular. That seems like an architectural problem that can also be solved in a monolith.

Try to run your monolith in kubernetes, it's possible but not much fun. Since single machines can not longer scale at large, we have to run distributed software, small pieces across hundreds or thousands of machines in order to scale efficiently.

> But in general, I have never seen a company that switched to micro-services, and didn’t end up regretting it a few years later

Netflix?

[woutr_be]

> This is unavoidable for many companies, since the code bases are far to large for any single person to grasp them all.

That's true, but this was the takeaway from the entire article:

> "When we remove that feeling of “I need to know how allllll of this works, but just enough so that I can rescue it when it breaks”, we facilitate the mental room to iterate on our team’s systems with greater depth."

To me it sounds like they've now introduced exactly that feeling with micro-services, developers now need to know how all services and front-ends work, and how they interact with each other.

Maybe the article is poorly structured, but if that's the entire takeaway from moving to micro-services and micro-frontends, then I do question their choice.

> Netflix

https://www.youtube.com/watch?v=CZ3wIuvmHeM

Netflix is indeed one example. It's hard to argue it doesn't work, but from my experience, it never worked out the way it was envisioned.