Circuit breaker pattern in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of the circuit breaker pattern in microservices?

Imagine you have many small services talking to each other. Sometimes one service might be slow or broken. What does the circuit breaker pattern mainly help with?

A It balances the load evenly across all service instances.

B It encrypts the communication between microservices for security.

C It prevents a failing service from being called repeatedly to avoid system overload.

D It automatically restarts failed services to recover them.

💡 Hint

Think about how to stop repeated failures from making things worse.

The circuit breaker pattern stops calls to a failing service after a threshold to prevent cascading failures and system overload.

❓ Architecture

intermediate

Which component is responsible for tracking failures in a circuit breaker implementation?

In a circuit breaker, one part counts how many times a service call fails. Which component does this?

A The API gateway encrypts failure data for security.

B The load balancer tracks failures to redirect traffic.

C The service registry keeps failure counts for each service.

D The failure counter inside the circuit breaker monitors failed calls.

💡 Hint

Focus on the part that decides when to open the circuit.

The failure counter inside the circuit breaker tracks failed calls to decide when to open the circuit and stop calls.

❓ scaling

advanced

How does the circuit breaker pattern help improve system scalability under high load?

When many users use a system, some services might slow down or fail. How does the circuit breaker help the system handle more users smoothly?

A By stopping calls to failing services, it frees resources to serve healthy requests faster.

B By duplicating requests to multiple services to increase throughput.

C By caching all responses to avoid calling services again.

D By automatically adding more service instances when failures occur.

💡 Hint

Think about how stopping bad calls helps the system breathe.

When the circuit breaker stops calls to failing services, it prevents resource waste and allows the system to serve healthy requests efficiently, improving scalability.

❓ tradeoff

advanced

What is a key tradeoff when setting the failure threshold in a circuit breaker?

Choosing how many failures trigger the circuit breaker is tricky. What is the main tradeoff?

A A low threshold may cause false alarms; a high threshold may delay failure detection.

B A low threshold causes data loss; a high threshold causes data duplication.

C A low threshold increases network traffic; a high threshold reduces security.

D A low threshold improves caching; a high threshold slows down encryption.

💡 Hint

Think about reacting too quickly versus too late.

If the failure threshold is too low, the circuit breaker may open unnecessarily (false alarms). If too high, it may keep calling a failing service too long, causing more problems.

❓ estimation

expert

Estimate the maximum number of failed requests allowed before the circuit breaker opens, given these parameters:

A circuit breaker is configured with a failure threshold of 5 failures within a 1-minute window. If the service receives 100 requests per minute and 4% of requests fail, how many failed requests will occur before the circuit breaker opens?

A 1 failed request

B 5 failed requests

C 4 failed requests

D 20 failed requests

💡 Hint

Calculate 4% of 100 requests, then compare to threshold.

4% of 100 requests = 4 failures per minute, which is below the threshold of 5. The circuit breaker opens only after 5 failures.

Practice

1. What is the primary purpose of the circuit breaker pattern in microservices?

easy

A. To prevent repeated calls to a failing service and improve system stability

B. To increase the speed of database queries

C. To encrypt communication between services

D. To balance load evenly across servers

Solution

1. Step 1: Understand the problem circuit breaker solves

   The circuit breaker pattern stops calls to a failing service to avoid cascading failures.

2. Step 2: Identify the main benefit

   This pattern improves system stability by preventing repeated failures and allowing recovery.

3. Final Answer:

   To prevent repeated calls to a failing service and improve system stability -> Option A

4. Quick Check:

   Circuit breaker purpose = prevent repeated failing calls [OK]

Hint: Circuit breaker stops calls to failing services fast [OK]

Common Mistakes:

• Confusing circuit breaker with load balancing
• Thinking it speeds up database queries
• Assuming it encrypts data

2. Which of the following correctly represents the three states of a circuit breaker?

easy

A. START, STOP, PAUSE

B. ACTIVE, INACTIVE, PENDING

C. CLOSED, OPEN, HALF_OPEN

D. ON, OFF, WAIT

Solution

1. Step 1: Recall circuit breaker states

   The circuit breaker has three states: CLOSED (normal), OPEN (blocking calls), HALF_OPEN (testing recovery).

2. Step 2: Match states to options

   Only CLOSED, OPEN, HALF_OPEN lists these exact states.

3. Final Answer:

   CLOSED, OPEN, HALF_OPEN -> Option C

4. Quick Check:

   States = CLOSED, OPEN, HALF_OPEN [OK]

Hint: Remember states as Closed, Open, Half-Open [OK]

Common Mistakes:

• Mixing up state names with unrelated terms
• Using generic terms like ON/OFF
• Forgetting the HALF_OPEN state

3. Consider this pseudocode for a circuit breaker:

if state == 'OPEN':
  return 'fail fast'
elif state == 'HALF_OPEN':
  if test_call_successful():
    state = 'CLOSED'
  else:
    state = 'OPEN'
else:
  call_service()

What happens when the circuit breaker is in HALF_OPEN state and the test call fails?

medium

A. The state changes to CLOSED and service calls continue

B. The state remains HALF_OPEN and retries immediately

C. The service call is ignored without state change

D. The state changes back to OPEN and calls are blocked

Solution

1. Step 1: Analyze HALF_OPEN state logic

   In HALF_OPEN, a test call checks if the service recovered. If it fails, the state changes to OPEN.

2. Step 2: Understand consequence of failure

   Changing to OPEN blocks further calls to prevent overload.

3. Final Answer:

   The state changes back to OPEN and calls are blocked -> Option D

4. Quick Check:

   HALF_OPEN fail -> OPEN state [OK]

Hint: Failed test call in HALF_OPEN resets to OPEN [OK]

Common Mistakes:

• Assuming state changes to CLOSED on failure
• Thinking retries happen immediately in HALF_OPEN
• Ignoring state changes on test failure

4. A developer implemented a circuit breaker but notices it never transitions from OPEN to HALF_OPEN. What is the most likely cause?

medium

A. The timeout to switch from OPEN to HALF_OPEN is missing or too long

B. The service calls are always successful

C. The circuit breaker is stuck in CLOSED state

D. The test call in HALF_OPEN always succeeds

Solution

1. Step 1: Understand OPEN to HALF_OPEN transition

   The circuit breaker moves from OPEN to HALF_OPEN after a timeout period to test recovery.

2. Step 2: Identify cause of no transition

   If the timeout is missing or set too long, the breaker stays OPEN indefinitely.

3. Final Answer:

   The timeout to switch from OPEN to HALF_OPEN is missing or too long -> Option A

4. Quick Check:

   Missing timeout blocks OPEN -> HALF_OPEN transition [OK]

Hint: Check timeout settings for OPEN to HALF_OPEN switch [OK]

Common Mistakes:

• Assuming success of service calls affects OPEN state
• Confusing CLOSED and OPEN states
• Ignoring timeout mechanism

5. You design a microservice system with a circuit breaker protecting a payment service. The circuit breaker trips (opens) after 5 failures within 1 minute and stays open for 2 minutes before trying again. What is the main tradeoff of setting the open duration too long?

hard

A. Long open duration improves user experience by retrying quickly

B. Long open duration reduces load on failing service but increases request failures for users

C. Long open duration causes the circuit breaker to never open

D. Long open duration increases the number of successful calls

Solution

1. Step 1: Understand open duration effect

   A long open duration blocks calls longer, reducing load on the failing service.

2. Step 2: Identify user impact

   While protecting the service, users experience more failures because calls are blocked longer.

3. Final Answer:

   Long open duration reduces load on failing service but increases request failures for users -> Option B

4. Quick Check:

   Long open = less load, more user failures [OK]

Hint: Long open = safer service, worse user experience [OK]

Common Mistakes:

• Thinking long open improves user experience
• Assuming circuit breaker never opens with long duration
• Believing long open increases successful calls