System Design: Defeating the SMS Retry Storm!
System Design: Defeating the SMS Retry Storm!
1,000 login requests hit your backend in one second. Your SMS provider only accepts 100. So what happens to the other 900?
This is one of the most underrated system design problems out there, and it shows up the moment your app comes back from an outage. Everyone logs in at once, and the "obvious" fixes quietly make things worse. Reject the extra requests and frustrated users smash resend until they DDoS you. Queue everything and codes arrive expired and useless.
So which path would you take, and is there a smarter third option? Drop your answer in the comments before you watch.
?Subscribe to KodeKloud for more system design, backend, and DevOps breakdowns.
#SystemDesign #RateLimiting #BackendDevelopment #SoftwareArchitecture #Coding #DevOps
1,000 login requests hit your backend in one second. Your SMS provider only accepts 100. So what happens to the other 900?
This is one of the most underrated system design problems out there, and it shows up the moment your app comes back from an outage. Everyone logs in at once, and the "obvious" fixes quietly make things worse. Reject the extra requests and frustrated users smash resend until they DDoS you. Queue everything and codes arrive expired and useless.
So which path would you take, and is there a smarter third option? Drop your answer in the comments before you watch.
?Subscribe to KodeKloud for more system design, backend, and DevOps breakdowns.
#SystemDesign #RateLimiting #BackendDevelopment #SoftwareArchitecture #Coding #DevOps
KodeKloud
...