A bug in the GitHub's Rate Limiter
System Design for SDE-2 and above: https://arpitbhayani.me/masterclass
System Design for Beginners: https://arpitbhayani.me/sys-design
Redis Internals: https://arpitbhayani.me/redis
Build Your Own Interpreter / Redis / DNS / BitTorrent / SQLite - with CodeCrafters.
Sign up and get 40% off - https://app.codecrafters.io/join?via=...
Rate limiters are essential to keep any product stable and away from abuse and GitHub like any other company did the same. But when they implemented their Rate Limiter using Redis, they saw pretty weird but interesting behaviors.
In this video, we understand how they implemented Rate Limiter and go in-depth about what happened, why it happened, and how they fixed it.
Recommended videos and playlists
If you liked this video, you will find the following videos and playlists helpful
System Design: • PostgreSQL connection management and ...
Designing Microservices: • Advantages of adopting a microservice...
Database Engineering: • How nested loop, hash, and merge join...
Concurrency In-depth: • How to write efficient and fair multi...
Research paper dissections: • The Google File System - Paper Explained
Outage Dissections: • Dissecting GitHub Outage and things t...
Hash Table Internals: • Internal Structure of a Hash Table
BitTorrent Internals: • Introduction to BitTorrent and the pr...
Things you will find amusing
Knowledge Base: https://arpitbhayani.me/knowledge-base
Bookshelf: https://arpitbhayani.me/bookshelf
Papershelf: https://arpitbhayani.me/papershelf
Other socials
I keep writing and sharing my practical experience and learnings every day, so if you resonate then follow along. I keep it no fluff.
LinkedIn: / arpitbhayani
Twitter: / arpit_bhayani
Weekly Newsletter: https://arpit.substack.com
Thank you for watching and supporting! it means a ton.
I am on a mission to bring out the best engineering stories from around the world and make you all fall in
love with engineering. If you resonate with this then follow along, I always keep it no-fluff.