Why Circuit breaker pattern in HLD? - Purpose & Use Cases

The Big Idea

What if your system could protect itself from crashing when one part fails?

The Scenario

Imagine you have a busy restaurant kitchen where orders keep coming in nonstop. If one station breaks down, the whole kitchen slows or stops, causing delays and unhappy customers.

The Problem

Without a way to detect and isolate the broken station, the kitchen staff wastes time trying to fix it while orders pile up. This causes long waits and sometimes the entire kitchen shuts down.

The Solution

The circuit breaker pattern acts like a smart kitchen manager who notices when a station is failing and temporarily stops sending orders there. This prevents the whole kitchen from getting overwhelmed and allows time to fix the problem.

Before vs After

✗ Before

callService(); // keep calling even if failing

✓ After

if (circuitBreaker.isClosed()) { callService(); } else { fallback(); }

What It Enables

This pattern enables systems to stay responsive and recover gracefully even when parts fail.

Real Life Example

In online shopping, if the payment service is down, the circuit breaker stops sending payment requests and shows a friendly message instead of freezing the whole checkout process.

Key Takeaways

Manual retries can overload failing services and cause system-wide issues.

Circuit breaker detects failures and stops calls to protect the system.

It helps maintain system stability and improves user experience during outages.