<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rate-Limiter on System Design</title><link>https://system-design.devops-monk.com/tags/rate-limiter/</link><description>Recent content in Rate-Limiter on System Design</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 30 May 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://system-design.devops-monk.com/tags/rate-limiter/index.xml" rel="self" type="application/rss+xml"/><item><title>Design a Rate Limiter</title><link>https://system-design.devops-monk.com/2026/05/design-a-rate-limiter/</link><pubDate>Sat, 30 May 2026 12:00:00 +0000</pubDate><guid>https://system-design.devops-monk.com/2026/05/design-a-rate-limiter/</guid><description>It&amp;rsquo;s 11:59 PM on Black Friday. Your e-commerce platform has been running smoothly all day. Then at midnight, 500,000 shoppers simultaneously hammer your /checkout API. Your servers start queuing requests. Then they start dropping requests. Then they crash. Every second of downtime costs thousands of dollars in lost sales.
Meanwhile, a competitor&amp;rsquo;s site — running the exact same infrastructure — handles the load just fine. The difference? They had a rate limiter.</description></item></channel></rss>