liveBook · Manning

Risk

As explained in Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

Deployment risk is the possibility that releasing a software change will cause failures or disruption in an application.

Deployment risk is the possibility that releasing a software change causes failures or disruption. Microservices reduce its scope by allowing one service to change without risking the entire application. section 1.9

Reduced deployment risk has practical operational effects:

  • A faulty update may break one part of the application rather than bring down the whole system. section 1.9
  • Teams can roll back a small part of the system instead of reverting the entire application. section 1.9
  • Smaller recovery scope supports more frequent deployments and a faster development pace. section 1.9

How Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform covers it

How deep it goes
Explains localized failures and rollback consequences but stops short of prescribing deployment procedures.
Examples
Uses service updates, partial application failures, and rolling back a small system part as concrete examples.
What you can do after
Evaluate how service boundaries can localize failures and make rollbacks smaller.
How it connects
Connects deployment risk with microservices, distributed applications, reliability, scalability, and frequent deployments.

Also explained in

Compare how 8 books explain risk →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform. The section links point to the parts of the book it draws on.