How to Start Using Microservices
This is complete bullshit, top to bottom.<p>Microservices add complexity, they don&#x27;t remove it.<p>Monolithic architecture doesn&#x27;t force tight coupling. Tight coupling doesn&#x27;t depend on an architecture. Making a monolith crash-proof is easier than dealing with intermittently-functioning microservices.<p>Being able to change microservices without that affecting any other services is a design goal, not an architectural feature.<p>Microservices are not inherently more scalable than monoliths. They have to be designed that way. And monoliths can equally well be designed to be scalable (just add more instances!).<p>When to use microservices? When one part of your monolith can easily be broken out and run on its own server as a service, and that would improve some performance bottleneck that you need because you can see a point where it will matter in the near future. Otherwise &quot;never&quot;.