Blast radius means how much of a system is affected when something goes wrong.

Think of dropping a stone into water:

        πŸ’₯
      (   )
    (       )
  (           )

The bigger the affected area, the bigger the blast radius.

Software example

Suppose your application has:

Auth
Users
Posts
Comments
Notifications

If a bug in the Posts module only breaks posts:

Posts πŸ’₯
Users       βœ…
Comments    βœ…
Notifications βœ…

β†’ Small blast radius

But if everything depends directly on one shared module and a bug there breaks the entire application:

Auth          ❌
Users         ❌
Posts         ❌
Comments      ❌
Notifications ❌

β†’ Large blast radius

Why developers care

A good architecture tries to limit blast radius.

For example:

  • modular architecture β†’ failures stay more isolated

  • feature flags β†’ disable one feature without taking down everything

  • independent services β†’ one service can fail while others continue

  • retries/timeouts β†’ prevent one failing dependency from taking down the whole system

Simple definition:

Blast radius = the scope of damage caused by a failure or change.

You can also hear it in security: β€œIf this account is compromised, what’s its blast radius?” β€” meaning what can the attacker affect?


Software-Development My-Journey-In-Codeless