Can you link to any resource? What I read from Fowler is that he has lots of reservations about it. To quote: Any architectural style has trade-offs: strength

Can you link to any resource? What I read from Fowler is that he has lots of reservations about it. To quote: Any architectural style has trade-offs: strengths and weaknesses that we must evaluate according to the context that it's used. This is certainly the case with microservices. While it's a useful architecture - many, indeed most, situations would do better with a monolith.[1] He even states that you never should start building your application as microservices, but instead as a monolith. So my primary guideline would be don't even consider microservices unless you have a system that's too complex to manage as a monolith. The majority of software systems should be built as a single monolithic application. Do pay attention to good modularity within that monolith, but don't try to separate it into separate services.[2] __ 1. https://martinfowler.com/articles/microservice-trade-offs.html https://martinfowler.com/articles/microservice-trade-offs.ht... 2. https://martinfowler.com/bliki/MicroservicePremium.html https://martinfowler.com/bliki/MicroservicePremium.html