Blast radius

As explained in Google Anthos in Action

Blast radius is the scope of components, users, or functionality affected by a failure or operational change.

How Google Anthos in Action covers it

How deep it goes

Defines outage scope and connects it to separate compilation and deployment, stopping short of a formal measurement method.

Examples

Uses payment and taxation services to show domain separation and single-microservice outage containment.

What it assumes

Assumes familiarity with service domains, APIs, independent deployment, and container-based operations.

What you can do after

Apply it via microservice boundaries and independent deployment to reduce outage scope and scale services separately.

How it connects

Connects microservices with service boundaries, containers, scalability, high availability, and Kubernetes recovery capabilities.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformThe blast radius is the extent of system impact caused by a failed change, measured by the number or criticality of affected components.
• 

  liveBookmanning.com
  Troubleshooting Java, Second EditionBlast radius is the scope of components, records, or systems affected by a failure or data problem.
• 

  liveBookmanning.com
  Platform Engineering on KubernetesBlast radius is the extent of systems, resources, or users that can be affected by a failure or security compromise.

Compare how 4 books explain blast radius →

Related concepts

• canary deploymentaddressed by · A canary deployment is a release strategy that exposes a change to a limited portion of users, traffic, or infrastructure before expanding it more broadly.
• rolling updateaddressed by · A rolling update is a deployment or upgrade technique that updates or replaces instances or resources incrementally rather than all at once, allowing the rest of the system to continue operating during the change.
• isolationaddressed by · Isolation is the separation of components, processes, resources, or contexts to limit interaction, interference, or the propagation of effects between them.
• couplingused by · Coupling is the degree of dependency between software components, including how their behavior, availability, or changes affect one another.
• sandboxingaddressed by · Sandboxing is the isolation of software execution in a restricted environment that limits its access to resources and its effects on surrounding systems.

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