Zero-Configuration (Auto-Provisioning): No manual setup required. The component automatically initializes circuits the moment you first call them in your code.
Dual-Storage Strategy:
DB Mode: Ensures Global Consistency across all front-ends/containers—if one trips, they all trip.
RAM Mode: Offers Near-Zero Latency by evaluating state in local memory. Ideal for ultra-high-volume traffic where every millisecond counts.
The QA Playground: A dedicated "Chaos Engineering" Backoffice. Manually simulate failures, force-open circuits, and verify UI fallbacks without waiting for a real-world outage.
Role-Based Governance: Secure administrative actions with the CircuitBreaker_Admin role, ensuring only authorized users can override system states in Production.
CircuitBreaker_Admin
The Gatekeeper: Place the IsAvailable action at the start of your integration logic.
IsAvailable
The Feedback Loop: Report successes or failures using the Update action (ideally within your Global Exception Handler to catch timeouts).
Update
The Recovery: Once the Cooldown Period expires, the circuit enters a Half-Open state, cautiously allowing a trial request to see if the service has recovered.
Unlike basic implementations, this component is designed for Scalability. Whether you are running on a single O11 front-end or a massive ODC container cluster, you have the flexibility to choose between Strong Consistency (DB) or Isolated Performance (RAM).
Stop relying on hope. Start designing for failure.