Why microservices might be finished as monoliths return with a vengeance

What an appallingly bad article. It starts with a premise only backed with an unsubstantiated and outright false appeal to authority (&quot;the likes of Amazon are moving to monoliths!1&quot;) and proceeds to list a few traits that are so wrong they fall into the &quot;not even wrong&quot; territory. For example, things like &quot;incorrect boundary domains&quot; and circular dependencies are hardly related to how distributed services are designed.<p>This nonsese reads like a badly prompted machine-generated text.

Is data integrity strictly a microservices problem? I swear I&#x27;ve seen a ton of monoliths with not-demoralized databases where it&#x27;s fairly confusing as to what column is correct since there&#x27;s a bunch of conflicting entries.<p>I&#x27;m a bit surprised that data migration is considered a problem for microservices. Is any &quot;class&quot; in the application allowed to create SQL statement? It seems like it&#x27;d be super easy to lift db functions to a microservice and replace the monolith&#x27;s SQL calls with HTTP (?) calls.

&quot;Return&quot;?<p>I&#x27;m an independent developer right now, building systems for businesses and there is literally no better way to deliver line-of-business internal applications than via a monolith.<p>Even the biggest corps still have only 20k employees or so; that&#x27;s far from the limits of a single VM&#x27;s capabilities.

I keep hearing monoliths are returning, without any indication of what has improved to make big single apps more manageable? All the same problems are there, so seems like this is just fashion trends tbh.<p>Yes if you have some small saas app don&#x27;t go crazy with tiny interdependent services prematurely. But if&#x2F;as you grow in team size, functionality, get out of here with your &quot;majestic monoliths&quot;.

Why Hand Tools May Be Finished As Table Saw Sales Increase

This topic has become click bait for engineers. The right answer is almost always just medium sized services drawn up from the data boundary.<p>This stuff isn’t rocket science

From my perspective, the Internet is strung together by a bunch of micro services - DNS here, email there, etc. etc. And that seems to work. They even seem to work together for the most part. I&#x27;m surprised that there have been all these problems with micro services, have they been overdoing the &quot;micro&quot; part?

Many microservices have no reason to exist in first place, they are a solution looking for a problem, that many folks don&#x27;t master modular programming, or love monkey patching, so a network layer or OS IPC is placed among them.<p>However, those same folks usually never learned about distributed computing, now their spaghetti code is done via OS IPC or networking calls, with all the &quot;fun&quot; that is debugging distributed systems.<p>They are also a way to sell cloud business, and consulting hours (also have myself to blame here), so if that is what folks want, that is what they get.

Microservices being used as the hammer for all nails spelled doom for at least one project I’ve worked around.<p>Just use your head and not the hype. The real value provided is modularity but you cannot forget the need to trace across a system when things go wrong or how performance might be impacted negatively.

Choosing between microservices and monoliths is like choosing between a hammer and a nail. You need both

Huh? Monoliths never went away in the first place so not really news IMHO.

The echo chamber is strong in this one