Microservices is the buzzword in software development. But most new projects should start as well-structured monoliths.
When to start as monolith
- Small team
- New product iterating fast
- Business domain not yet clear
- Tight budget and timelines
When to consider microservices
- Large teams deploying independently
- System parts with very different scalability needs
- Clear business domain with defined boundaries
- Mature DevOps infrastructure
The pragmatic path
Start as a modular monolith. Extract microservices only when a part needs independent scaling.
