Circuit breaker pattern in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the state when the circuit breaker stops calls temporarily.

Microservices

circuit_breaker_state = "[1]"

Drag options to blanks, or click blank then click option'

Aopen

Bclosed

Chalf-open

Ddisabled

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'closed' which means calls are allowed.

Choosing 'half-open' which is a testing state.

The open state means the circuit breaker stops calls temporarily to prevent failures.

2fill in blank

medium

Complete the code to check if the circuit breaker allows calls in the {{BLANK_1}} state.

Microservices

if circuit_breaker_state == "[1]":
    allow_calls = True
else:
    allow_calls = False

Drag options to blanks, or click blank then click option'

Afailed

Bopen

Cclosed

Ddisabled

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'open' which blocks calls.

Choosing 'disabled' which is not a standard state.

The closed state means the circuit breaker allows calls to pass through normally.

3fill in blank

hard

Fix the error in the code to transition from open to half-open state after timeout.

Microservices

if time_since_open > timeout:
    circuit_breaker_state = "[1]"

Drag options to blanks, or click blank then click option'

Aclosed

Bopen

Cdisabled

Dhalf-open

Attempts:

3 left

💡 Hint

Common Mistakes

Setting state back to 'open' which keeps blocking calls.

Setting state to 'closed' without testing.

After the timeout, the circuit breaker moves to half-open to test if the service has recovered.

4fill in blank

hard

Fill both blanks to complete the logic for recording failures and opening the circuit breaker.

Microservices

failure_count += 1
if failure_count [1] failure_threshold:
    circuit_breaker_state = "[2]"

Drag options to blanks, or click blank then click option'

A>=

B<

Copen

Dclosed

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' which never triggers opening.

Setting state to 'closed' which allows calls.

When failures reach or exceed the threshold, the circuit breaker moves to open state to stop calls.

5fill in blank

hard

Fill all three blanks to complete the dictionary comprehension that tracks service status with circuit breaker states.

Microservices

service_status = {service: [1] for service, state in services.items() if state [2] "[3]"}

Drag options to blanks, or click blank then click option'

Astate.upper()

B==

Copen

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' which selects wrong services.

Not converting state to uppercase.

This comprehension selects services where the state is open and converts the state to uppercase for status.

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