System Design for Beginners: arpitbhayani.me/sys-design
System Design for Experienced Engineers: arpitbhayani.me/masterclass
Redis Internals: arpitbhayani.me/redis
Build Your Own Redis / DNS / BitTorrent / SQLite - with CodeCrafters.
Sign up and get 40% off - app.codecrafters.io/join?via=...
In this video, I covered the concept of throttling and rate limiting to ensure system stability. Throttling controls the flow of data to prevent system overload, with strategies like slowing down, rejecting, or ignoring requests. Rate limiters play a crucial role in managing incoming requests to avoid system abuse, handle traffic surges, control consumption costs, and prevent cascading failures. I discussed five use cases, including preventing DDoS attacks, managing user surges, internal rate limiting for pricing tiers, controlling costs with third-party APIs, and protecting databases from heavy deletions.
Recommended videos and playlists
If you liked this video, you will find the following videos and playlists helpful
System Design: • PostgreSQL connection ...
Designing Microservices: • Advantages of adopting...
Database Engineering: • How nested loop, hash,...
Concurrency In-depth: • How to write efficient...
Research paper dissections: • The Google File System...
Outage Dissections: • Dissecting GitHub Outa...
Hash Table Internals: • Internal Structure of ...
Bittorrent Internals: • Introduction to BitTor...
Things you will find amusing
Knowledge Base: arpitbhayani.me/knowledge-base
Bookshelf: arpitbhayani.me/bookshelf
Papershelf: 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: arpit.substack.com
Thank you for watching and supporting! it means a ton.
Негізгі бет Ғылым және технология Why, where, and when should we throttle or rate limit?
Пікірлер: 24