<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>System Design on Nalar</title>
    <link>https://nalar.dev/tags/system-design/</link>
    <description>Recent content in System Design on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/system-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Token Bucket Rate Limiting for Controlled Bursts</title>
      <link>https://nalar.dev/token-bucket-rate-limiting-for-controlled-bursts/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/token-bucket-rate-limiting-for-controlled-bursts/</guid>
      <description>&lt;h1 id=&#34;token-bucket-rate-limiting-for-controlled-bursts&#34;&gt;Token Bucket Rate Limiting for Controlled Bursts&lt;/h1&gt;&#xA;&lt;p&gt;A service may handle 100 requests per second comfortably on average while still needing to accept a short burst of 300 requests after a client reconnects. A rigid per-second limit treats those situations as the same problem: once the current window is full, otherwise acceptable work is rejected.&lt;/p&gt;&#xA;&lt;p&gt;Token bucket rate limiting gives you a more useful control. It separates two decisions: &lt;strong&gt;how quickly permission to do work is replenished&lt;/strong&gt; and &lt;strong&gt;how much permission may accumulate for a burst&lt;/strong&gt;. Once you understand those two numbers, you can reason about the limiter without depending on a particular library or platform.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
