> 1) something has different run time needs than something else. This is supposedly the #1 technical reason to move to microservices: horizontal scaling + dist

> 1) something has different run time needs than something else. This is supposedly the #1 technical reason to move to microservices: horizontal scaling + distributed system (in the rare cases the app needs low latency across the world) The other one is being able to reuse services, whether provided by third parties or that you can download from docker hub/GitHub and run yourself. > 2) Something needs to be developed by a different team and for whatever reasons you don't want those teams to be too dependent. This is supposedly the single core reason to adopt microservices architecture. This is what says on the tin. If you want to have multiple teams work independently on separate components, they need to be loosely coupled deployed independently. This is not brain surgery. > Everything else is just needlessly/prematurely increasing overhead, deployment friction, etc. What else is there? The rationale for microservices was from the start organizational, with a lesser scope on operations/technical aspects.