A blast radius describes how much of a system is affected when something goes wrong.
It captures the scope and impact of a failure which components break, which users are affected, and how far the damage spreads beyond the original fault.
A small blast radius means failures are contained and isolated. A large blast radius means a single issue can cascade across services, teams, or customer journeys.
From a testing perspective, understanding blast radius helps prioritise risk. Testing focuses not just on whether a component can fail, but on how much harm that failure can cause and how well the system contains it.
Reducing blast radius relies on isolation, boundaries, and graceful degradation so that failures remain local instead of becoming system-wide incidents.
It captures the scope and impact of a failure which components break, which users are affected, and how far the damage spreads beyond the original fault.
A small blast radius means failures are contained and isolated. A large blast radius means a single issue can cascade across services, teams, or customer journeys.
From a testing perspective, understanding blast radius helps prioritise risk. Testing focuses not just on whether a component can fail, but on how much harm that failure can cause and how well the system contains it.
Reducing blast radius relies on isolation, boundaries, and graceful degradation so that failures remain local instead of becoming system-wide incidents.
