<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rate-Limiting on Lorbic</title><link>http://localhost:1313/tags/rate-limiting/</link><description>Recent content in Rate-Limiting on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 07 Jul 2026 17:00:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/rate-limiting/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing a Distributed Rate Limiter with Redis</title><link>http://localhost:1313/designing-a-rate-limiter/</link><pubDate>Tue, 07 Jul 2026 17:00:00 +0530</pubDate><guid>http://localhost:1313/designing-a-rate-limiter/</guid><description>&lt;p>There is a class of bugs that only happen at midnight.&lt;/p>
&lt;p>Your API has a rate limit: 1000 requests per minute. A client hits 999 at 11:59:59 PM, then fires another 999 at 12:00:00 AM. Two windows, two clean counters, all 1998 requests allowed. Your database gets a spike it was never designed to handle, and you spend the next hour wondering how your rate limiter let this through.&lt;/p>
&lt;p>It did let it through. You just did not know it.&lt;/p></description></item></channel></rss>