<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api-Security on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/api-security/</link>
    <description>Recent content in Api-Security on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/api-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nginx vs Caddy vs Envoy Ratelimit: Best Self-Hosted Rate Limiting Solutions 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-28-nginx-vs-caddy-vs-envoy-ratelimit-self-hosted-rate-limiting-guide-2026/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-28-nginx-vs-caddy-vs-envoy-ratelimit-self-hosted-rate-limiting-guide-2026/</guid>
      <description>&lt;p&gt;Rate limiting is a fundamental defense mechanism for any service exposed to the internet. It protects your infrastructure from abuse, prevents resource exhaustion, and ensures fair access for all users. Whether you are running a public API, a web application, or a microservices architecture, implementing effective rate limiting is not optional — it is essential.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
