Using NGINX limit_req to Shield APIs from Traffic Bursts
Learn how NGINX's limit_req module uses a leaky‑bucket filter to throttle API traffic, with a concrete configuration, trade‑offs, and verification steps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how NGINX's limit_req module uses a leaky‑bucket filter to throttle API traffic, with a concrete configuration, trade‑offs, and verification steps.
When Twitter API v2 returns HTTP 429 Too Many Requests, the app has hit a rate limit. This guide walks you through diagnosing the exact cause, checking the relevant headers, and applying the right backoff strategy to keep your integration running smoothly.
X API v2 list endpoints are cursor-based with no offsets. Compare cursor pagination, time-windowed backfill, and streaming, then implement a resumable paginator and validate completeness.
Learn how to navigate Behance’s pagination, respect its rate‑limits, and build a resilient client with a hands‑on Node.js example. Understand headers, backoff, and token refresh to keep your app running smoothly.
Notion's API uses cursor-based pagination on all list endpoints. A single request misses data past 100 rows. This post shows a robust generator pattern handling pagination, rate limits, recursive blocks, and deduplication—with a Python example.
Configure Envoy's local token bucket rate limit filter with per-client keying, shadow-mode rollout, xDS updates, and verification via admin stats and access logs — plus the pitfalls that silently disable it.
NGINX's limit_req module smooths abusive traffic with a leaky bucket — but the defaults (503 rejections, no burst, IP keys behind a load balancer) are subtly wrong for most APIs. Here's a config that works and how to verify it.
A step‑by‑step guide to identify why you receive 429 Too Many Requests on the recent search endpoint and how to fix it safely.
Local rate limits silently scale with your replica count. Envoy's global rate limiting centralizes quota decisions in an external gRPC service — here's how the pieces fit, a working per-IP example, and the fail-open vs. fail-closed decision you can't skip.