Give Me Back My Monolith
I don&#x27;t think I blame the author at all. I&#x27;m not sure why you would start with microservices, unless you wanted to show that you could build a microservices application. Monoliths are quicker and easier to setup when you&#x27;re talking about a small service in the first place.<p>It&#x27;s when an organization grows and the software grows and the monolith starts to get unwieldy that it makes sense to go to microservices. It&#x27;s then that the advantage of microservices both at the engineering and organizational level really helps.<p>A team of three engineers orchestrating 25 microservices sounds insane to me. A team of of thirty turning one monolith into 10 microservices and splitting into 10 teams of three, each responsible for maintaining one service, is the scenario you want for microservices.