A few issues with the design: 1. Redis is a single point of failure 2. Redis will become a bottleneck when the system scales to handle millions of clients
Configuring rate limiter in a distributed systems are not so easy and maintaining them is additional overhead , and there are instance we mark legitimate users as malicious which misleads and causes losses in legitimate network traffic ,also DDoS attackers can take advantage of mimicking such system.
![Jack Harlow - Hello Miss Johnson [Official Music Video]](http://i.ytimg.com/vi/Q86_nlRoIGw/mqdefault.jpg)
Please continue the series
Can't you use redis itself for cached rules? What if common redis cluster crashes in distributed environment?
videos are amazing, and i would request you to upload videos faster
Hi,NIKHIL i will surely watch your whole series on system design, But i have a request can i have one of Ferrari from your wall? 😅
Thank you, very well explained
How many parts left in this video series?
A few issues with the design:
1. Redis is a single point of failure
2. Redis will become a bottleneck when the system scales to handle millions of clients
Shai hnnn bro
great
Configuring rate limiter in a distributed systems are not so easy and maintaining them is additional overhead , and there are instance we mark legitimate users as malicious which misleads and causes losses in legitimate network traffic ,also DDoS attackers can take advantage of mimicking such system.
people even do custom implement of these algorithms at gateway level, which is a stupidity.
bhai directly system design interview by Alex xu see hi pel diya 🤦♂
Yes
That is a great book to learn about these designs