I think some of these points are gross exaggerations.
> You immediately increase the things your servers have to do tenfold.
Really? It's ten times as much work to implement microservices?
> Personally, I’ve seen slowdowns on the order of 1000% when moving to microservices (yes, ten times slower).
Then you implemented your microservices wrong.
I think that the author's understanding of the goals and purposes of microservices is maybe a bit misguided. Microservices are about front-loading scaling problems, not about having a clean architecture or smaller codebase. If you never need to scale, you don't need microservices (but you're probably wrong).
The flowchart at the end of the post really underscores for me that this author's argument is not genuine. He holds up this shibboleth of a "monolithic" architecture, something that doesn't really exist in 2015.
> You immediately increase the things your servers have to do tenfold.
Really? It's ten times as much work to implement microservices?
> Personally, I’ve seen slowdowns on the order of 1000% when moving to microservices (yes, ten times slower).
Then you implemented your microservices wrong.
I think that the author's understanding of the goals and purposes of microservices is maybe a bit misguided. Microservices are about front-loading scaling problems, not about having a clean architecture or smaller codebase. If you never need to scale, you don't need microservices (but you're probably wrong).
The flowchart at the end of the post really underscores for me that this author's argument is not genuine. He holds up this shibboleth of a "monolithic" architecture, something that doesn't really exist in 2015.