The main problem with microservices is simply that most people don't understand how to design them correctly. A poorly designed monolith is pretty much always

The main problem with microservices is simply that most people don't understand how to design them correctly. A poorly designed monolith is pretty much always going to be superior to a poorly designed microservices architecture. The floor protecting you from bad design is significantly higher. The biggest mistake is that people tend to create services that are far too small, and too many of them. Then it gets chatty and you develop a distributed spaghetti code. Or failing to divide them into coherent domains. Or overindexing on scaling individual functions/cost rather than logical boundaries You should almost always err towards services that are too large rather than too small. You can always subdivide further later on. I interview tons of senior engineers and managers from reputable companies that describe designs that would produce immense technical debt