Blast radius

The share of users that a single failure, bad deployment or migration can hurt. Cells, shards, per-team databases and staged rollouts cap it, so that incidents become partial instead of total.

Where it shows up in real systems

  • Cell router

    In a cell-based architecture the whole stack is copied into cells that share nothing. The router is the only shared part, so it must be tiny and extremely reliable; a bad deployment then affects one cell instead of every customer.

    In production: AWS cell-based architecture, Slack cells, DoorDash cells, Route 53 Application Recovery Controller

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox