4 ms·
I think this, approaching DDD, is the most common reason engineers push for it these days.
by guywhocodes 6y ago
I think this, approaching DDD, is the most common reason engineers push for it these days.
- pknopf 6y agoIt isn't worth the added friction though. And if you happen to leak concerns in your services (in a monolith), it's really easy to adjust, as opposed to having to coordinate the deployment of 5+ services. And even then, a distributed monolith is still a risk. Micro-services add cement to your project. Be prepared to keep boundaries you write for a long time.
- curryst 6y agoAnother reason is that it gives you more agency to adjust your code. Want to refactor? Cool, I don't have to talk to 15 teams about how this might impact them. Same thing with changing a schema, changing scaling strategies, etc, etc. I can do things in 2 weeks that would take 2 weeks of just talking to people on a monolith. That might be more organizational than a technical limit, but I've never seen an agile monolith before.