The thing with microservices is that each one comes with a real cost, an amount of friction that gets contributed to your overall process flow. At some point, this frictive energy becomes intense enough that it jeopardizes the project.
I think "microservices" is a sane architectural pattern for some applications. The problem is that people polarize into one extreme or the other, and many attempts at a microservice implementation that I see would more rightly be classified "nanonservices"; things are broken up, almost at random, into tiny, disjunct, co-dependent pieces. This is a total nightmare scenario, and a monolith would undoubtedly be better.
I think "microservices" is a sane architectural pattern for some applications. The problem is that people polarize into one extreme or the other, and many attempts at a microservice implementation that I see would more rightly be classified "nanonservices"; things are broken up, almost at random, into tiny, disjunct, co-dependent pieces. This is a total nightmare scenario, and a monolith would undoubtedly be better.