The document discusses circuit breakers and their importance for distributed systems. It notes that failures are difficult to detect in distributed systems and that retrying calls against an unresponsive subsystem can lead to resource shortages or cascading failures. It then introduces the circuit breaker pattern, which detects failures and prevents retrying the same failing action until the service recovers, in order to avoid cascading failures. The circuit breaker can be in an open, closed, or half-open state depending on success or failure detection.

1. Circuit Breaker
?
Serverless on AWS
lessons learned #4
Are you really
production-ready?

2. In distributed systems
it is hard to tell when
and how* other
components fail.
*we don’t ask if - they will!

3. A large number of
calls or retries against
an unresponsive
subsystem can cause
resource shortages or
even worse:
cascading failures

4. cascading failures

5. Circuit Breaker

6. The Circuit Breaker
detects failures and
prevents retrying the
same failing action.
Until the unresponsive
service has recovered.

7. OPEN
CLOSED
HALF
OPEN
success
persistent
failure
detected
failure
re-open
after delay
Circuit Breaker

8. Circuit Breaker applied

9. Circuit Breaker

10. thumbs up, comment, share
What are your thoughts?
Is anything important missing?
If you liked it, please leave a comment.
connect with me!