Any microservices discussion that does not take into account both infrastructure complexity and team size is incomplete. For small teams and small&#x2F;not complex infrastructures, it&#x27;s always a bad idea. The premium that is paid for switching to microservices is great indeed and it&#x27;s paid in <i></i>much<i></i> slower development and deployment times. This happens as soon as you start breaking an application apart, so even with only a couple of &quot;mini&quot; services, much of the price has been paid.<p>Since the author doesn&#x27;t mention either, I can&#x27;t conclude anything, but it&#x27;s very possible that the team he was advising didn&#x27;t follow his advice because it was stupid and didn&#x27;t take into account the above two factors.<p>See obligatory reading:<p><a href="http:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;MonolithFirst.html" rel="nofollow">http:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;MonolithFirst.html</a><p><a href="http:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;MicroservicePremium.html" rel="nofollow">http:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;MicroservicePremium.html</a><p>EDIT: Spacing