Building a rate limiter, why even use Redis.

<p>Two months ago I shipped UNPWNED, a passive web security scanner aimed at indie hackers and developers shipping AI-generated code (Cursor, Lovable, Bolt, Replit, v0).</p> <p>I

<p>If your API has no rate limiting, any client can send as many requests as it wants. A broken retry loop, a scraper, or a user who refreshes too fast all of it hits your server

<h2> 1. Intro — The Problem We Actually Had </h2> <p>Building real-time systems is often presented as a distributed systems problem.</p> <p>Kafka, stream processors, event buses,

<p>Every backend engineer has heard the advice: add a cache. It will make your system faster. And they are right, it will. But a cache that is not properly understood is one of

<h2> What I Built </h2> <p><strong>Resilix</strong> is an ultra-high-performance, enterprise-grade distributed Token-Bucket Rate Limiter and Request Deduplicator middleware

<h2> Problem Statement </h2> <p><strong>Rate limiting</strong> is a technique that controls how many requests a user or system can make to a server within a specific timeframe.

<p><a href="https://leetdezine.com/?utm_source=devto" rel="noopener noreferrer">LeetDezine</a><br /> <a class="article-body-image-wrapper"

<p>Hey dev.to community! 👋</p> <p>I've been working on a side project for a while now and finally got it to a point where I feel comfortable sharing it publicly. It's called