The term 'microservices ' implies going ham with little networked backends while pretending like distributing logic in this way has no costs. Independently developed and deployed backends have a time and place, but it certainly is a costly pattern that should be used as a last resort. I have yet to see a case at any scale where backend code should not be developed together in a monolithic codebase, even when it is deployed in a distributed architecture for various needs (job processing vs request/reply backends).

Replies (3)

The notion of microservices is a lazy event pipelining architecture. It's better to just use a RTC microkernel framework inside your application and break out scalable pieces with proxy placeholders or a pub-sub rally point like over zmq or redis.
Default avatar
G Force G 4 months ago
Micro services seems to be just another instance of Conway's Law. Some organizations are composed of many many single responsibility teams and so they evangelize that the way to do things is their way.