tag: rate-limiting
articles: 5 · beats: 2
latest: November 15, 2026
---
Rate Limiting
5 Crashtech articles on Rate Limiting, spanning System Design & Architecture and Development Best Practices, published between August 2026 and November 2026. Every piece is full-text HTML with sources, structured data and an authored FAQ.
They span System Design & Architecture (4), Development Best Practices (1). System Design & Architecture Development Best Practices

Scale an API by Removing Contention: Stateless Workers, Safe Caches, and Bounded Queues
A practical API scaling sequence: remove instance-local state, cache only safe responses, bound work queues, and shed excess load before dependencies fail.
Rate Limiting Strategies Explained: Token Bucket, Leaky Bucket and Sliding Windows
How rate limiters protect backend systems from cascading collapse, compare algorithms for burst tolerance and fairness, and handle distributed Redis state.
Scaling the API Layer: Stateless Servers, Rate Limits, Caching and Async Work
The API tier is the easy part to scale, if you keep it stateless. The practices that matter: limits, pagination, caching, queues and graceful overload.
The Strange HTTP Status Codes: 451, 418, 420, 218 and 530, and What They Teach
Five odd status codes, which are standard, which are jokes and which are vendor inventions, and why custom codes are a trap for client code.
Token Buckets: Bounding Rate Limits at the Edge
Fixed-window counters leak at boundaries. Token buckets refill steadily, absorb bursts, and bound the sustained rate strictly—the algorithm Stripe uses.
Questions we answer about Rate Limiting
- Does stateless mean an API has no state?
- Should every API response be cached?
- Why can a queue make an overloaded API worse?
- What is the difference between Token Bucket and Leaky Bucket?
- Why is Fixed Window Counter vulnerable to traffic spikes?
- How do distributed rate limiters avoid race conditions in Redis?
- What HTTP headers should an API return when rate limiting?
- Why must API servers be stateless to scale?
- How should an API respond when it is overloaded?
- What can an API cache safely?
Covered alongside
Frequently asked questions
What does Crashtech publish about Rate Limiting?
5 articles tagged Rate Limiting, the most recent published November 15, 2026. They span System Design & Architecture (4), Development Best Practices (1). Each carries numbered sources, an authored FAQ and full structured data.
What questions about Rate Limiting does Crashtech answer directly?
10 questions have a dedicated answer page under this tag, including “Does stateless mean an API has no state?”. Each answer is authored prose from the article it belongs to, not a generated summary.
Can AI assistants read Crashtech's Rate Limiting coverage?
Yes. Crashtech serves full static HTML to every crawler, allows all major AI user agents in robots.txt, and publishes an llms.txt manifest plus a full-text corpus, so assistants can retrieve and cite these articles directly.