Circuit Breaker Patterns
Quick Reference
What & Why
Definition
>= 75% of service-to-service calls protected by circuit breakers (Istio, Envoy, Resilience4j) preventing cascade failures.
Business Value
Improves system uptime from 99.5% to 99.9% and reduces blast radius of failures by 70% through circuit breakers and chaos engineering validation Achieving >= 75% calls have circuit breakers is a key milestone toward this goal.
Context
This capability is part of the Acceleration milestone's focus on scale automation, embed compliance, improve speed & reliability. Essential for teams targeting MTTR, CFR improvements.
Success Criteria
>= 75% calls have circuit breakers
Measurement
Circuit breaker coverage across service mesh
Evidence
- Service mesh config
- Circuit breaker trip logs
- Cascade failure prevention metrics
In Practice
Real-World Implementation
Teams configure circuit breakers: trip after 5 consecutive failures, half-open after 30s, close after 3 successes. Prevents cascade during dependency outages.
Concrete Example
Implementation Guide
Implementation Steps
Follow the measurement approach: Circuit breaker coverage across service mesh
For detailed step-by-step guidance, refer to the Resilient Operations & Chaos Engineering Implementation Kit.
Resources
Implementation Kit
Resilient Operations & Chaos Engineering KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Complementary
Often adopted together, from the Resilient Operations & Chaos Engineering epic
Troubleshooting & FAQs
Common Issues
Issue: Target metric not improving
Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness
Issue: Team resistance to adoption
Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition
Issue: Inconsistent implementation across teams
Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards
Frequently Asked Questions
Can we implement this before completing prerequisites?
While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.
How long does implementation typically take?
Most capabilities can be implemented within 90 days when tackled as part of the Acceleration milestone. Individual timelines vary based on team size and existing practices.