Course contentsShow
← System Design
Lesson 1083 of 1,91927. Circuit Breakers and BulkheadsFree lesson

Graceful Degradation Strategies

Designing systems to degrade gracefully by shedding non-critical features when dependencies fail, preventing total collapse.

Graceful Degradation Strategies

What You'll Learn

You'll learn how to design systems that shed non-essential features when dependencies fail, keeping core functionality alive instead of collapsing entirely.

The Core Idea

When a critical dependency fails (database, cache, external API), you have two choices: crash completely or degrade gracefully. Graceful degradation means consciously deciding which features to turn off, which to simplify, and which to protect at all costs.

Think of it like a ship taking on water. Instead of letting the entire vessel sink, you seal off non-critical compartments (the gym, the lounge) to keep the bridge and engine room operational. Your users notice reduced service, but they still reach their destination.

How It Works

Identify your critical path (what was taught in lesson 1082): determine which features are absolutely essential. A shopping site must let users checkout, but product recommendations are nice-to-have.

When a dependency fails:

  • Disable optional features entirely (turn off recommendations)
  • Switch to simpler alternatives (serve cached data instead of fresh queries)
  • Return partial results (show 10 products instead of 100)
  • Use stale data temporarily (yesterday's inventory counts)

Example Hierarchy

  1. Critical: Payment processing, order submission
  2. Important: Product search, inventory checks
  3. Optional: Personalized recommendations, reviews, related products

When your recommendation engine goes down, you don't take the whole site offline—you just hide that section and keep selling.

Integration with Resilience Patterns

Graceful degradation works alongside circuit breakers (which detect failures) and bulkheads (which contain them). The circuit breaker opens, preventing further damage. Your degradation strategy decides what happens next.

Key Takeaway: Graceful degradation transforms catastrophic failures into temporary inconveniences by prioritizing core functionality and shedding non-critical features when dependencies fail.