> In my experience, having small manageable code bases that are responsible for one domain makes things so much easier to develop and maintain. I think everybo

> In my experience, having small manageable code bases that are responsible for one domain makes things so much easier to develop and maintain. I think everybody agrees with that. The issue is that architecting your system like that on a code / repo level means that you gain the complexity of having to manage dependencies between your components, and it complicates the deployment story. microservices then further complicates things by requiring you to be able to independently deploy each service. this is a lot of complexity to manage for something that doesn't directly solve any problems in your business domain. This reaction you are seeing is because people have now had enough time to actually work on and hear about projects that were built using microservices. Many of them have found that they don't deliver on their promises, because of the reasons mentioned in the article.