Microservices are just managers codifying the boundaries of their kingdom.
Large groups operating well together without clearly defined boundaries of responsibility is very much the exception rather than the norm and always has been.
The dysfunctionality of middle management outweighed economies of scale for a long time but I doubt it will last forever.
I consider microservices a natural extension of OOP on a service level. Each microservice functions like an abstract object that represents a thing. Of course it has the same drawback as OOP, do it too much, or implement it too little and you got problems.
But even ignoring that, you fail to see that OOP is also a form of management concept. Its still compartmentalization and abstraction such that no developer must understand the full state of the system to make sense of an api.
OOP is much more a huaman management and communication concept than a technical one.
- microservices is not a tech concept, it's a management concept
We (devs) like to think that microservices is all about tech, but in reality it's a disguised tech concept used by management to:
- grow the team. We are going to need more devs to build more microservices!
- have more things to manage. Like, do you really think managers want to say "yeah, I manage the delivery of... a library". At the end of the quarter they want to say: "yeah, I manage the delivery of a service that..."
- get salary raises. See previous point
That's it. The tech industry is shifting (has shifted already?) from a "tech people know better. Let them drive the big decisions" perspective to a "lean managers drive tech decisions because they know Agile and Agile is good" one.
Microservices is all about management/organizational topics, not about tech.