Design Rate Limiter : step-3 of 4 (PART-I) - Design Deep Dive & LYFT 🚕🚖

Channel:

codestorywithMIK

Subscribers:

92,300

Published on June 26, 2022 5:08:03 AM ● Video Link: https://www.youtube.com/watch?v=APayGQDMIwo

Duration: 7:59

323 views

23

In this video we will see step-3 (PART-I) of 4 steps to design a service called "Rate Limiter". 
In this video, we do a deep dive into the Design of Rate Limiting Service.
Bonus : We will also see a real life example of a service called "Lyft" and take a look at its Rate Limiting Rules.

We will also answer many Questions that are generally asked in System Design Interview for Rate Limiter like :
- How are rate limiting rules created ?
- Where are those rules stored ?
- When a request is throttled (rate limited), what will you do with that request ?
- How does the client know that its request has been throttled (rate limited) ?
- How does the client know the number of allowed remaining requests before being throttled (rate limited) ?

Kindly make use of topic wise Pointers below. Hope that helps 😇

Introduction : (00:00)
Rate Limiting Rules : (00:30)
LYFT Rate Limiting Rule : (01:22)
Exceeding The Rate Limit : (04:45)
HTTP Response Headers of Rate Limiter : (06:07)

My GitHub Repo for interview preparation : https://github.com/MAZHARMIK/Interview_DS_Algo
Subscribe to my channel : https://www.youtube.com/channel/UCaw58edcO3ZqMw76Bvs0kGQ?sub_confirmation=1