<?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 Pi Stack</title><link>https://www.pistack.xyz/tags/rate-limiting/</link><description>Recent content in Rate-Limiting on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/rate-limiting/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted Rate Limiting &amp; API Throttling: NGINX vs Traefik vs Envoy vs Kong 2026</title><link>https://www.pistack.xyz/posts/self-hosted-rate-limiting-api-throttling-nginx-traefik-envoy-kong-guide-2026/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-rate-limiting-api-throttling-nginx-traefik-envoy-kong-guide-2026/</guid><description>&lt;p>Rate limiting is the unsung hero of infrastructure reliability. Without it, a single misbehaving client can exhaust your server resources, trigger cascading failures, and bring down your entire stack. Yet most rate limiting guides point you toward expensive cloud APIs or managed services that charge per-request and lock you into a vendor.&lt;/p></description></item></channel></rss>