← All labsSimulation
Blast radius
What actually stops working when this component dies?
A three-tier system you can break. Fail a component or a whole zone, compare production with dev, and switch the service names between AWS, Azure and GCP.
Loading lab
How the model works
Each component declares its dependencies as groups: every group needs at least one working member. Status is computed from that graph on every click, so the result is derived and not scripted.
What it leaves out
- Availability only. It does not model overload, though surviving replicas may saturate in a real failure.
- Failover is treated as instant. Real database promotion interrupts writes briefly.
- A single region. Multi-region adds data-consistency decisions this model leaves out.
Covers
- High availability
- Multi-cloud mapping
- Environment comparison
- Dependency analysis