Content deleted Content added
Removed uncited content. Made the tone more neutral |
Jaredririe (talk | contribs) No edit summary |
||
(5 intermediate revisions by 4 users not shown) | |||
Line 1:
{{Short description|Software development pattern}}
The '''Circuit
The circuit breaker pattern can be used in conjunction with other patterns, such as retry, fallback, and timeout, to enhance fault tolerance in systems. <ref>{{Cite book |title=Kubernetes Native Microservices with Quarkus and MicroProfile |publisher=Manning |year=2022 |isbn=9781638357155}}</ref>
Line 15:
=== Closed state ===
When everything is normal, the circuit breakers
▲[[File:Circuit Breaker -Closed state.png|thumb|Circuit Breaker Closed State]]
{{clear}}
=== Open state ===
In this state circuit breaker returns an error immediately without even invoking the services. The Circuit breakers move into the ''half-open'' state after a timeout period elapses. Usually, it will have a monitoring system where the timeout will be specified.
▲[[File:Circuit Breaker -Openstate.png|thumb|Circuit Breaker Open State]]
{{clear}}
=== Half-open state ===
In this state, the circuit breaker allows a limited number of requests from the service to pass through and invoke the operation. If the requests are successful, then the circuit breaker will go to the ''closed'' state. However, if the requests continue to fail, then it goes back to
▲[[File:Circuit Breaker -Half Open state.png|thumb|Circuit Breaker Half Open State]]
==References==
|