exponential backoff
Waiting progressively longer between retries, for example 1, 2, then 4 seconds, so a struggling service gets room to recover.
In more detail
The delay usually doubles after each failed attempt, up to a maximum. Adding some randomness, called jitter, stops many clients from retrying at the same moment and overwhelming a service that is trying to recover.
Example
The course models backoff with a chain of Kafka retry topics.Related terms
- retry — Sending a request again after it failed or timed out, in the hope that it succeeds the second time.
- jitter — A random amount added to or taken from a retry delay so that many clients do not all retry at the same moment.
- Retry-After — The response header that tells a client how long to wait, in seconds or as a date, before trying again.
- retry budget — A cap on retries measured as a fraction of normal traffic, so retries cannot overwhelm a failing dependency.
- retry topic — A topic that holds records whose processing failed so they can be tried again later without blocking the main topic.
- transient failure — A failure caused by a temporary condition, such as a brief network glitch, that may succeed if simply tried again.
Taught in
- When The Call Fails — AI Engineering: LLM Apps, RAG & Agents
- Working With AI Coding Assistants — AI Engineering: LLM Apps, RAG & Agents
- Databases That Survive: Standbys, Replicas And Global Tables — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Retry That Overtook — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Built-in Rate Limiting Middleware — Modern .NET Core, C# & Enterprise Microservices
- Retry and Circuit Breaker Policies with Polly — Modern .NET Core, C# & Enterprise Microservices
- Retries With Backoff Topics — Apache Kafka & Event Streaming
- Retries, Backoff And Jitter — Scalable System Design & Distributed Architecture
References
- Retry pattern
- Polly: retry strategy
- AWS Architecture Blog: Exponential Backoff and Jitter
- Amazon Builders' Library: Timeouts, retries, and backoff with jitter
- AWS Prescriptive Guidance: retry with backoff