Risk & Resilience Engineering

When to use

"Use when a system must continue functioning despite failures. Design for graceful degradation — when a component fails, the system degrades (slower, fewer features) rather than crashing. Build in redundancy, circuit breakers, and fallbacks."

Example

"A web application's database fails. Without resilience, the application crashes. With resilience — read requests fall back to a cache (stale but functional), write requests are queued for later processing, users see a degraded-experience banner. The system survives the failure."

Common misuse

"Designing for reliability (preventing failure) without designing for resilience (surviving failure). Failures will happen; a system that cannot survive them is fragile regardless of how rarely it fails."

Also known as

Related models