11 ms·
What? This comment seems ridiculous to me. They aren't a panacea and aren't right in all circumstances, but they have plenty of technical advantages. You can wr
by baumy 8y ago
What? This comment seems ridiculous to me. They aren't a panacea and aren't right in all circumstances, but they have plenty of technical advantages. You can write code for different services in different languages / on different stacks, prototype using a new language/technology/stack with a small piece of the overall application, develop and deploy in parallel more easily, if one component fails it's less likely to bring down the whole application, gives you more freedom to scale if certain components of an application require more resources or different types of resources than others....
That's off the top of my head. These all come with tradeoffs of course, but to say they bring nothing to the table is absurd.
- Udik 8y ago> You can write code for different services in different languages But wouldn't that mean that the services must have no code whatsoever in common? And in that case, why would they be part of a monolith in the first place?