Retries consume capacity and can multiply across service layers. Bound attempts, use backoff and preserve the original deadline.
Before you start
You should understand HTTP, database transactions and the difference between one process and independently failing services. Draw the participants and message direction before choosing a pattern. Include timeout, duplicate delivery and recovery in the model instead of considering only successful requests.
The practical goal is to reason through this situation: Three attempts at each of three layers can greatly amplify one failing user request. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Identify eligible failures
Separate transient faults from validation or authorization failures.
Step 2: Control amplification
Choose retry ownership and bound attempts within the overall deadline.
Step 3: Preserve operation identity
Use idempotency and jitter where repeated attempts could overload or duplicate effects.
Worked scenario
Three attempts at each of three layers can greatly amplify one failing user request.
Three layers each making three attempts can produce up to 27 deepest calls for one request. During an outage, that increases load precisely when capacity is constrained. Place retries deliberately and expose budget exhaustion rather than allowing every layer to independently start a new full retry sequence.
Common mistake
Retrying every error includes permanent validation failures.
Verify the behavior
Count downstream attempts during failure and verify the global deadline remains respected.
Interview exercise
Place retries deliberately.
Answer and reasoning
Retry transient eligible operations at a chosen layer with jitter, budget and idempotency; expose exhaustion clearly.
Continue learning
Compare the scenario with the Microservices interview questions and test your understanding with the Microservices MCQs. For terminology and implementation details, consult the reference material.