Architecture debates get tribal fast. Strip the fashion away and one question remains: does the architecture match the size and shape of your organization?
The cost side of microservices
Every service boundary adds network latency, partial failure modes, versioning contracts and operational surface. A team of eight maintaining thirty services spends most of its week on plumbing instead of product.
When a modular monolith wins
Below roughly fifteen to twenty engineers, a well modularized monolith with clear internal boundaries deploys faster, debugs easier and costs a fraction. You can still split out genuinely independent pieces, like heavy media processing, when the need is real.
Split services along organizational seams, not along the nouns in your database diagram.
Signals you are ready to split
- Teams block each other on deploys every week.
- One module has wildly different scaling or security needs.
- You can name the two teams who will own each side of the boundary.
The best architecture is the one your team can operate on its worst week. Complexity is a cost center; spend it where it buys real autonomy.
