4 ms·

This should get more emphasis. Microservices do require more overhead. Additionally, they require you to be familiar enough with you business logic to know whe

This should get more emphasis. Microservices do require more overhead. Additionally, they require you to be familiar enough with you business logic to know where you boundaries lie - changing abstraction boundaries is much harder with microservices than with a monolith. I think that while they are great for scaling, they are a lot harder to use to successfully get off the ground (though I'm betting that there are places that have successfully done so)

ben_jones 9y ago
You also have to know how to "do" microservices. Whether it's incorporating message queues like RabbitMQ, protocols like gRPC, etc., it's very hard to get right the first time by winging it without previous experience. Redesigning microservices after is a PITA.
- mcginleyr1 9y ago
  100% agree. Your path is based on your teams experience and capabilities, not trends.