liveBook · Manning

Blast radius

As explained in The Coder Cafe

Blast radius is the extent of systems, users, or functionality affected by a failure or change.

Blast radius is the extent of systems, users, or functionality affected by a failure or change. Reducing it makes changes safer, increases confidence, and enables faster iteration. section 6.14.2

Limit blast radius with controlled change strategies:

  • Use feature flags to enable or disable functionality without deploying new code, supporting experimentation and quick rollbacks. section 6.14.2
  • Use canary releases for limited rollouts to a small, controlled subset of production. section 6.14.2
  • Use progressive rollouts to increase scope gradually across clusters or regions. section 6.14.2
  • Use shadow testing to run changes alongside production traffic without affecting real users. section 6.14.2

How The Coder Cafe covers it

How deep it goes
Defines the affected scope and gives four rollout techniques, but does not quantify blast radius or provide a measurement procedure.
Examples
Uses feature toggles, limited production subsets, clusters or regions, and parallel production traffic as concrete change scenarios.
What you can do after
Apply feature flags, canary releases, progressive rollouts, and shadow testing to reduce change-related impact.
How it connects
Connects blast radius with feature flags, canary releases, progressive rollouts, shadow testing, observability, and simulation.

Also explained in

Compare how 8 books explain blast radius →

Related concepts

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