Graceful Degradation
A strategy where a system continues to function with reduced capability when a component fails, instead of crashing entirely. Show cached results when the database is down.
What is Graceful Degradation?
A strategy where a system continues to function with reduced capability when a component fails, instead of crashing entirely. Show cached results when the database is down.
Graceful Degradation is a advanced concept that sits in the Reliability & Resilience area of system design. Engineers reach for it whenever they need to reason about real-world trade-offs in that space — not just for textbook correctness, but because real production systems at companies like Netflix, Amazon, and Google make these decisions every day.
If you want to go deeper than this definition — with diagrams, code, and a quiz to lock it in — work through the "Graceful Degradation" lesson linked below. It walks through the why, the mechanism, the trade-offs, and how the giants actually use it in production.
Learn Graceful Degradation in depth
Full interactive lesson with diagrams, code examples, real-world references, and a quiz.
Open the Graceful Degradation lessonRelated lessons
Lessons that touch on Graceful Degradation as part of a larger topic.
Graceful Degradation
When parts of your system fail, give users a reduced experience instead of a broken one
intermediate · microservices architecture
Fault Tolerance
Design systems that continue operating when components fail, redundancy, isolation, and graceful degradation
advanced · reliability resilience
Online-First Architecture
Traditional web architecture where the server is the source of truth and offline is handled as a graceful degradation
intermediate · web content delivery
See also
Related glossary terms you might want to look up next.
Circuit Breaker
A pattern that stops calling a failing service after repeated failures, preventing cascade failures. Like an electrical circuit breaker that cuts power to prevent fires.
Fault Tolerance
A system's ability to keep operating correctly even when some of its components fail. Achieved through redundancy, replication, and graceful degradation.
Bulkhead
A pattern that isolates different parts of a system so a failure in one part doesn't sink the whole ship. Named after the compartments in a ship's hull.