Operational burden is the extra work needed to run and maintain a system. Microservices bring a substantial baseline of that work in exchange for independent scalability. section 12.3.3
Running microservices safely takes more than writing business logic:
- Build automated CI/CD pipelines, centralized logging, and distributed network monitoring. section 12.3.3
- Manage container orchestration platforms such as Kubernetes. section 12.3.3
When the premium may be worth paying
For a small team or simple application, infrastructure work can crowd out feature development. Start with a well-structured modular monolith; consider microservices when deployment friction grows with team size or a module needs very different scaling hardware. section 12.3.3


