graceful degradation
Continuing to work with reduced features when part of the system fails, instead of failing completely.
In more detail
If the status service is down, the dashboard still shows the user and stats with a degraded flag rather than a 500 error. Fallbacks such as default values, cached data or queued work are how a service degrades gracefully.
Related terms
- Backend for Frontend — A small backend service built for one specific frontend, which gathers data from other services and shapes it exactly for that frontend’s screens.
- circuit breaker — A wrapper around calls to another service that stops making calls for a while after repeated failures, so the failing service can recover.
- Promise.allSettled — A JavaScript function that waits for every promise in a list to finish and reports each one’s result, whether it succeeded or failed.
- soft dependency — A dependency you can do without by degrading, so its failure does not fail your request.
- load shedding — Deliberately rejecting some requests when overloaded so the requests that are accepted can still be served well.
Taught in
- API Gateway & BFF Patterns: Backend-for-Frontend — Production Full-Stack Engineering
- Resilience Engineering: Circuit Breakers & Retries — Production Full-Stack Engineering
- Full-Stack System Verification: Capstone Integration — Production Full-Stack Engineering
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Storage And Bandwidth — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Circuit Breakers — Scalable System Design & Distributed Architecture
- Backpressure And Load Shedding — Scalable System Design & Distributed Architecture
- Worked Design Two: A Global Chat System — Scalable System Design & Distributed Architecture
- Worked Design Two: Scaling Chat Fan Out — Scalable System Design & Distributed Architecture