The End of Microservices
Equating &quot;Microservices&quot; with &quot;Information Superhighway&quot; really shows the tech bubble that this article is written in.  &quot;Information Superhighway&quot; was a vacuous but mainstream term used by politicians and public figures.  &quot;Microservices&quot; is a tech hype train led by expensive consultants and pickaxe companies thriving off the current tech boom.<p>Don&#x27;t get me wrong, a service-oriented architecture is the only thing that scales to large companies.  Once you get to dozens of engineers and millions of lines of code you will inevitably need to have an SOA because Conway&#x27;s law.  Also, there is a learning curve to building microservices which improved tooling really helps with.<p>However the thing that really grates at me is how these articles say things like:<p>&gt; <i>Services are now an everyday, every-developer way of thinking</i><p>With nary a mention of the overhead.  There is no way around it, distributed systems have an irreducible complexity no matter how good your tooling and boilerplate is.  You have to put in extra work to decouple everything and handle failure in a way that actually reap the benefits of the distributed system.  And in the end, what these articles always gloss over is the interface between these systems.  If you can easily define an interface between systems that stays relatively stable as the service evolves, then congratulations, you have a good candidate for a service with minimal overhead.  But for most applications, those interfaces are shifting all the time, and there is no better tooling than multiple logical services running within one binary and build system where <i>integration testing and validation is cheap</i>.  This is a real fucking problem people, it&#x27;s not going to go away because there&#x27;s a couple billion dollars worth of venture-backed startups ready to blow their cash on you in the vain and most likely misplaced hope that they are actually going to <i>have to</i> scale to dozens of engineers.  Premature scalability is one of the worst siren songs for young engineers and we&#x27;re seeing it in spades right now.