Which scenario best describes when to use retry with exponential backoff in microservices?
easy📝 Conceptual Q2 of 15
Microservices - Resilience Patterns
Which scenario best describes when to use retry with exponential backoff in microservices?
AWhen a service permanently rejects a request due to invalid data
BWhen a service is temporarily unavailable due to high load
CWhen a service always returns success immediately
DWhen a service does not require any retries
Step-by-Step Solution
Solution:
Step 1: Identify retry use cases
Retry with exponential backoff is useful when failures are temporary, such as service overload or network issues.
Step 2: Match scenario to use case
When a service is temporarily unavailable due to high load describes temporary unavailability, which fits retry use. Options A, C, and D do not involve temporary failures suitable for retries.
Final Answer:
When a service is temporarily unavailable due to high load -> Option B
Quick Check:
Retry use case = Temporary failure [OK]
Quick Trick:Retry only for temporary failures, not permanent errors [OK]
Common Mistakes:
MISTAKES
Retrying on permanent errors
Retrying when service always succeeds
Ignoring when retries are unnecessary
Master "Resilience Patterns" in Microservices
9 interactive learning modes - each teaches the same concept differently