This really reads like a bad-faith interpretation of microservices. Of course microservices suck whenever someone starts a new one to do something that shares c

This really reads like a bad-faith interpretation of microservices. Of course microservices suck whenever someone starts a new one to do something that shares code or logic with already existing services. Likewise, of course monoliths suck when people just willy nilly add code and modules for each thing; low quality programming is low quality regardless of where it lives Real microservices implementations don't deliver so much from the proposed statement about synchronous web-tier request handling vs asynchronous compute workers in my experience. A few easy rules to guide this development are even touched on in the article, but treated like they could only ever be a tenet of monoliths. Very strange.