회로 차단기 상태 이해하기

In distributed systems, failures are inevitable. The Circuit Breaker pattern helps your applications gracefully handle these failures.

This lesson will guide you through the three fundamental states of a Circuit Breaker: Closed, Open, and Half-Open. Understanding these states is key to building resilient microservices.

Remember the Circuit Breaker pattern? It's like an electrical circuit breaker for your code.

• It detects when a remote service is failing.
• It 'trips' to prevent further calls to that failing service.
• It gives the failing service time to recover.

This prevents cascading failures and improves system stability.

A Circuit Breaker operates through three main states, each dictating how your application interacts with a potentially failing service:

• Closed: The normal operating state.
• Open: The state where calls are blocked due to detected failures.
• Half-Open: A transient state to test if the service has recovered.

Let's explore each state in detail!

The Closed state is the default state. It means everything is working normally.

• All requests to the protected service pass through.
• The Circuit Breaker continuously monitors for failures (e.g., timeouts, exceptions).
• If the number of failures crosses a predefined threshold, the Circuit Breaker 'trips' and transitions to the Open state.

In the Closed state, your application directly calls the service. Here's a simplified idea:

When the Circuit Breaker detects too many failures in the Closed state, it transitions to Open.

• In this state, all requests to the protected service are immediately blocked.
• Instead of making the actual call, the Circuit Breaker returns an error or a fallback response.
• This gives the failing service time to recover without being overloaded by more requests.

The primary purpose of the Open state is to prevent your application from repeatedly hitting a service that is already struggling or down.

• It saves resources (network, CPU) that would otherwise be wasted on failed calls.
• It prevents the failing service from being overwhelmed and potentially worsening its state.
• It introduces a 'cooling off' period for the service.

After a predefined timeout in the Open state, the Circuit Breaker moves to the Half-Open state.

• This is a crucial, temporary state.
• It allows a limited number of test requests to pass through to the protected service.
• These test requests determine if the service has recovered.

If the test requests succeed, the circuit closes. If they fail, it re-opens.

You've now learned the three core states of a Circuit Breaker!

• Closed: Normal operation, monitoring for failures.
• Open: Blocking all calls after too many failures, allowing recovery time.
• Half-Open: Allowing limited test calls to check for recovery.

These states work together to make your systems more robust and resilient against service outages. Next, we'll look at how to configure these states.