Circuit Breaking Patterns
What you'll learn: How circuit breakers automatically stop traffic to failing services to prevent cascading failures across your service mesh.
The Core Idea
A circuit breaker in a service mesh acts like an electrical circuit breaker in your home. When a service becomes unhealthy (too many errors, slow responses, or connection failures), the circuit breaker "trips" and temporarily blocks new requests to that service. This prevents your application from wasting resources on doomed requests and gives the unhealthy service time to recover.
Without circuit breakers, a single failing service can create a domino effect: requests pile up, threads get exhausted, timeouts cascade to other services, and soon your entire system grinds to a halt.
How Circuit Breakers Work
Circuit breakers monitor outbound connections and track failure rates. They operate in three states:
Closed (Normal): Requests flow normally. The breaker monitors for failures.
Open (Tripped): After exceeding failure thresholds, the breaker stops sending requests and immediately returns errors. This prevents resource exhaustion.
Half-Open (Testing): After a cooldown period, the breaker allows limited test requests. If they succeed, it closes; if they fail, it reopens.
Circuit Breaker Configuration
You typically configure:
- Consecutive errors threshold (e.g., 5 failures)
- Error percentage threshold (e.g., 50% failure rate)
- Check interval for monitoring
- Sleep window before trying again
- Connection pool limits per host
This builds on the retry policies and timeout configurations you've already learned, creating a complete resilience strategy.
Key Takeaway: Circuit breakers protect your service mesh from cascading failures by automatically detecting unhealthy services and temporarily halting traffic to them, giving both the failing service and your system resources time to recover.