> Microservices provide an abstraction. So do modules/classes/interfaces etc. You don't need a layer of HTTP in between components to have abstraction. In add

> Microservices provide an abstraction. So do modules/classes/interfaces etc. You don't need a layer of HTTP in between components to have abstraction. In addition, it feels like microservices solve a problem that very few people really have. I've never run into a case where I though "boy, I'd sure like to have a different database for this one chunk of code". If that did happen, then sure, split it out, but I can hardly believe that splitting your entire code base into microservices has a net benefit. The real problem in nearly every project I've worked on is complexity of business logic. A monolith is much easier to refactor, and you can change the entire architecture if you need to without having to coordinate releases of many different applications.