liveBook · Manning

Operational burden

As explained in Grokking Software Architecture

The additional work, resources, and complexity required to operate and maintain a software system.

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

How Grokking Software Architecture covers it

How deep it goes
Lists core infrastructure demands and explains their productivity cost for small teams and simple applications.
Examples
Contrasts small teams and simple applications with deployment friction or distinct scaling needs in larger systems.
What you can do after
Evaluate whether to keep a modular monolith or adopt microservices when deployment friction or scaling needs emerge.
How it connects
Connects microservices to monoliths, independent scalability, CI/CD pipelines, centralized logging, monitoring, and container orchestration.

Also explained in

Compare how 3 books explain operational burden →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.