<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api-Design on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/api-design/</link>
    <description>Recent content in Api-Design on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/api-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Rate Limiter Libraries: Bucket4j vs Resilience4j vs Governor vs Guava RateLimiter</title>
      <link>https://www.pistack.xyz/posts/2026-06-19-rate-limiter-libraries-bucket4j-resilience4j-governor-guava/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-19-rate-limiter-libraries-bucket4j-resilience4j-governor-guava/</guid>
      <description>&lt;p&gt;Every API needs rate limiting. Whether protecting against abuse, enforcing tiered pricing, or preventing cascading failures, rate limiters are the first line of defense for service reliability. While reverse proxies like Nginx and Envoy provide server-level rate limiting, application-level rate limiter libraries give developers fine-grained control — per-user quotas, dynamic limits, distributed coordination, and custom rejection strategies.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
