The Death of Microservice Madness in 2018
I think &quot;microservices&quot; is so appealing because so many Developers <i>love</i> the idea of tearing down the &quot;old&quot; (written &gt;12 months ago), &quot;crusty&quot; (using a language they don&#x27;t like&#x2F;isn&#x27;t in vogue) and &quot;bloated&quot; (using a pattern&#x2F;model they don&#x27;t agree with) &quot;monolith&quot; and turning it into a swarm of microservices.<p>As an Infrastructure guy, the pattern I&#x27;ve seen time and time again is Developers thinking the previous generation had no idea what they were doing and they&#x27;ll do it <i>way</i> better.
They usually nail the first 80%, then hit a new edge case not well handled by their architecture&#x2F;model (but was by the old system) and&#x2F;or start adding swathes of new features during the rewrite.<p>In my opinion, only the extremely good developers seem to comprehend that they are almost always writing what will be considered the &quot;technical debt&quot; of 5 years from now when paradigms shift again.