---
title: "Discussion on \"Why we need exponential backoff with jitter when retrying\" | Hashnode"
description: "Discussion on \"Why we need exponential backoff with jitter when retrying\". The problem\nYou want to retry an operation e.g. a network request. If you spam requests, you will overload the server and end up getting rate limited (429 too many requests).\nThis leads us to exponential backoff first. For every retry, we wait longer..."
url: "https://hashnode.com/posts/why-we-need-exponential-backoff-with-jitter-when-retrying/676e66d331fc2ea45e9345fc"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why we need exponential backoff with jitter when retrying](https://tigerabrodi.blog/why-we-need-exponential-backoff-with-jitter-when-retrying?utm_source=hashnode&utm_medium=feed)

The problem You want to retry an operation e.g. a network request. If you spam requests, you will overload the server and end up getting rate limited (429 too many requests). This leads us to exponential backoff first. For every retry, we wait longer...

Dec 27, 2024 · 4 min read · tigerabrodi.blog  
Read the article

-   [#apis](https://hashnode.com/tag/apis)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[Tiger Abrodi](https://hashnode.com/@tigerabrodi)

@tigerabrodi · Germany

  
[View profile](https://hashnode.com/@tigerabrodi)

Obsessed with crafting software.

Just a guy who loves to write code and watch anime.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.