Bird
Raised Fist0
Microservicessystem_design~10 mins

Timeout pattern in Microservices - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to set a timeout for a microservice call.

Microservices
response = service.call(request, timeout=[1])
Drag options to blanks, or click blank then click option'
A5s
B5
C5000ms
Dtimeout
Attempts:
3 left
💡 Hint
Common Mistakes
Using just '5' without units may cause errors.
Using variable names instead of actual timeout values.
2fill in blank
medium

Complete the code to handle a timeout exception in a microservice call.

Microservices
try:
    response = service.call(request, timeout=3000)
except [1]:
    handle_timeout()
Drag options to blanks, or click blank then click option'
AServiceUnavailable
BConnectionError
CTimeoutError
DValueError
Attempts:
3 left
💡 Hint
Common Mistakes
Catching unrelated exceptions like ValueError.
Not catching any exception leading to crashes.
3fill in blank
hard

Fix the error in the timeout retry logic code.

Microservices
for attempt in range(3):
    try:
        response = service.call(request, timeout=2000)
        break
    except [1]:
        if attempt == 2:
            raise
        wait_before_retry()
Drag options to blanks, or click blank then click option'
ATimeoutException
BTimeoutExpired
CTimeout
DTimeoutError
Attempts:
3 left
💡 Hint
Common Mistakes
Using non-existent exception names.
Not breaking the loop on success.
4fill in blank
hard

Fill both blanks to implement a timeout pattern with fallback and logging.

Microservices
try:
    response = service.call(request, timeout=[1])
except [2]:
    log_timeout()
    response = fallback_service.call(request)
Drag options to blanks, or click blank then click option'
A3000
BTimeoutError
C5000
DConnectionError
Attempts:
3 left
💡 Hint
Common Mistakes
Using wrong exception types.
Setting timeout as a string instead of number.
5fill in blank
hard

Fill all three blanks to create a timeout pattern with retry, timeout value, and exception handling.

Microservices
for i in range([1]):
    try:
        response = service.call(request, timeout=[2])
        break
    except [3]:
        if i == [1] - 1:
            raise
        wait_before_retry()
Drag options to blanks, or click blank then click option'
A3
B2000
CTimeoutError
D5
Attempts:
3 left
💡 Hint
Common Mistakes
Using wrong exception names.
Incorrect retry count or timeout values.

Practice

(1/5)
1. What is the main purpose of the timeout pattern in microservices?
easy
A. To cache responses from services to reduce load
B. To retry a failed request indefinitely until it succeeds
C. To stop waiting for a slow service after a set time to keep the system responsive
D. To encrypt communication between microservices

Solution

  1. Step 1: Understand the timeout pattern concept

    The timeout pattern is designed to limit how long a service waits for a response from another service.
  2. Step 2: Identify the main goal of this pattern

    Its goal is to keep the system responsive by not blocking resources waiting too long for slow services.
  3. Final Answer:

    To stop waiting for a slow service after a set time to keep the system responsive -> Option C
  4. Quick Check:

    Timeout pattern = stop waiting after set time [OK]
Hint: Timeout means stop waiting after a limit to stay responsive [OK]
Common Mistakes:
  • Confusing timeout with retry logic
  • Thinking timeout caches data
  • Assuming timeout encrypts data
2. Which of the following is the correct way to implement a timeout in a microservice call using pseudocode?
easy
A. response = callService().waitForever()
B. response = callService().withTimeout(5000ms)
C. response = callService().retryIndefinitely()
D. response = callService().cacheResponse()

Solution

  1. Step 1: Identify timeout syntax in pseudocode

    The correct way to set a timeout is to specify a maximum wait time, like withTimeout(5000ms).
  2. Step 2: Eliminate incorrect options

    response = callService().waitForever() waits forever, no timeout. response = callService().retryIndefinitely() retries indefinitely, not timeout. response = callService().cacheResponse() caches response, unrelated.
  3. Final Answer:

    response = callService().withTimeout(5000ms) -> Option B
  4. Quick Check:

    Timeout = withTimeout(time) [OK]
Hint: Timeout needs a max wait time method like withTimeout() [OK]
Common Mistakes:
  • Using infinite wait instead of timeout
  • Confusing retry with timeout
  • Mixing caching with timeout
3. Consider this pseudocode snippet for a microservice call with timeout:
try {
  response = callService().withTimeout(3000ms)
  print(response)
} catch (TimeoutException) {
  print("Service timed out")
}
What will be printed if the service takes 5 seconds to respond?
medium
A. "Service timed out" immediately after 3 seconds
B. No output, program hangs
C. The service response after 5 seconds
D. An error message unrelated to timeout

Solution

  1. Step 1: Analyze the timeout duration and service response time

    The timeout is set to 3000ms (3 seconds), but the service responds in 5 seconds, which is longer than the timeout.
  2. Step 2: Understand the catch block behavior

    When the timeout expires, a TimeoutException is thrown and caught, printing "Service timed out".
  3. Final Answer:

    "Service timed out" immediately after 3 seconds -> Option A
  4. Quick Check:

    Timeout triggers catch and prints timeout message [OK]
Hint: Timeout shorter than response triggers exception and catch [OK]
Common Mistakes:
  • Assuming response prints after full delay
  • Ignoring exception handling
  • Thinking program hangs forever
4. A developer wrote this code snippet to apply a timeout:
response = callService().timeout(2000ms)
print(response)
But the system never times out and waits indefinitely. What is the likely error?
medium
A. The method name should be withTimeout, not timeout
B. The timeout value 2000ms is too short to trigger
C. The print statement is missing inside a try-catch block
D. Timeouts only work with asynchronous calls

Solution

  1. Step 1: Check method naming conventions for timeout

    Common timeout methods use names like withTimeout. Using timeout may not apply the timeout correctly.
  2. Step 2: Evaluate other options

    Timeout value 2000ms is valid. Print outside try-catch won't prevent timeout. Timeouts can work synchronously or asynchronously depending on implementation.
  3. Final Answer:

    The method name should be withTimeout, not timeout -> Option A
  4. Quick Check:

    Correct method name applies timeout [OK]
Hint: Check method names carefully for timeout application [OK]
Common Mistakes:
  • Assuming timeout value too short to trigger
  • Ignoring method name correctness
  • Thinking print location affects timeout
5. You design a microservice system where Service A calls Service B, which calls Service C. To avoid cascading delays, you want to apply the timeout pattern effectively. Which strategy is best?
hard
A. Set equal timeout values on all calls regardless of call chain
B. Set a single long timeout only on Service A's call to B, ignoring B to C timeouts
C. Do not use timeouts; rely on retries to handle delays
D. Set a timeout on Service A's call to B, and also on B's call to C, each shorter than the caller's timeout

Solution

  1. Step 1: Understand cascading call delays

    Service A calls B, which calls C. If B waits too long for C, A's timeout may be exceeded.
  2. Step 2: Apply timeout pattern to prevent cascading delays

    Each service should have a timeout shorter than its caller's timeout to fail fast and avoid long waits.
  3. Final Answer:

    Set a timeout on Service A's call to B, and also on B's call to C, each shorter than the caller's timeout -> Option D
  4. Quick Check:

    Timeouts cascade with decreasing limits [OK]
Hint: Timeouts should cascade with shorter limits downstream [OK]
Common Mistakes:
  • Setting only one timeout ignoring nested calls
  • Using equal timeouts causing delays
  • Relying only on retries without timeouts