Monolith first
Building a new system as one deployable application and splitting it into services later, once the domain borders are known from real use.
Martin Fowler observed that most successful microservice systems started as a monolith that grew too big, while most systems built as microservices from scratch ran into trouble. The reason is bounded contexts: at the start nobody knows where the stable borders are, and moving a border inside one codebase is a refactor, while moving it between services is a migration.
The practical version is a modular monolith: one deployment, with modules that already respect context borders and do not share tables. Splitting a service out later is then cheap. Splitting early along guessed borders is how teams end up with a distributed monolith.
Sources
- Martin Fowler: Monolith First martinfowler.com
Related terms
- Modular monolith: One deployable application split inside into modules with clear boundaries, each owning its data and using the others only through defined interfaces.
- Microservices: An architecture where a system is built from small, separately deployed services, each owning its data and talking to the others over the network.
- Distributed monolith: Services that look separate but have to be changed, tested and deployed together, so you pay for microservices and still have a monolith.
- Bounded context: A part of a system where each business term has one meaning and one model, with explicit translation at its edges.
