Every engineer should know this (retries with jitter)

👉 Try Honeycomb: https://ui.honeycomb.io/signup?utm_source=fnf&utm_medium=youtube&utm_campaign=august&utm_term=ggadirov&utm_content=sign-up ======⚡⚡⚡====== Learn why exponential backoff without jitter causes retry storms and thundering herd failures and how full jitter and equal jitter fix it with five lines of code. This video breaks down the math, the code, and the charts behind backoff and jitter so your distributed systems stop synchronizing failures into outages. Consider becoming a member of the channel by joining me ❤️ https://www.youtube.com/channel/UCqAL_b-jUOTPjrTSNl2SNaQ/join ☕ Buy me a coffee: https://www.buymeacoffee.com/softwaredeveloperdiaries 🙌 Become my Patreon and get exclusive perks: https://patreon.com/softdevdiaries 💼 Follow me on LinkedIn and drop me a message if you'd like: https://www.linkedin.com/in/gadirovgs/ 💻 Also, let's connect on GitHub: https://github.com/gusgad 📚 Resources: Observability Engineering book: https://www.honeycomb.io/observability-engineering-oreilly-book Code: https://github.com/gusgad/youtube-tutorials/tree/retry-with-jitter 🕒 Timestamps: 0:00 Why exponential backoff alone isn't enough 4:06 Exponential backoff without jitter 5:32 Full jitter 7:52 Equal jitter And don't forget to subscribe for more videos like this 😊