Record success and failure signals for the protected dependency.
Circuit Breaker
Track failures and temporarily stop calls to an unhealthy dependency. Closed, open and half-open states let the system fail fast while still testing whether the dependency has recovered.
How can callers stop wasting time and capacity on a dependency that is likely to keep failing?GateSift summary based on Microsoft Azure Architecture Center guidance. The wording, visualization, Azure mapping and analyzer context are original GateSift material.
How Circuit Breaker works
Failure history determines whether a dependency call proceeds, fails immediately or probes for recovery.
Open the circuit when the failure threshold is exceeded and reject calls without waiting for timeouts.
Use a controlled half-open probe to close the circuit only after the dependency recovers.
What this pattern helps you decide
Track failures and temporarily stop calls to an unhealthy dependency. Closed, open and half-open states let the system fail fast while still testing whether the dependency has recovered.
Where you may see it
- Application resilience libraries such as Polly
- API gateway or service-mesh dependency protection
- Fail-fast wrappers around remote service calls
How the analyzers can surface it
- Retry loops without a long-failure protection strategy
- Backend failover or health-probe behavior in APIM
- Repeated connector failures without a cooldown or alternate path
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
This page links to Microsoft Azure Architecture Center for the source architecture guidance. GateSift summaries, diagrams, Azure examples and analyzer signals are original. No endorsement by Microsoft is implied.