seed-rate-limit-backoff

Handle HTTP 429 rate limit errors by wrapping your API calls in an exponential backoff function. This pattern pauses retries based on server Retry-After hints, applies jitter to prevent thundering herds, and safely caps total retry attempts.

Exponential backoff with jitter is a retry strategy that spaces out delayed HTTP requests using random intervals. Use it when calling APIs that return transient 5xx errors or rate limits to ensure system stability and avoid overwhelming the server.

Retry transient 5xx API errors safely by implementing a cap-based backoff pattern. This verifies retryability before attempting another request, respects Retry-After headers, and prevents endless loops or runaway resource consumption.

This backoff pattern works with any HTTP API that returns 429 rate limit or transient 5xx errors. It specifically honors Retry-After headers when present and includes a testable reference implementation written in TypeScript.

Naive API retries cause thundering herds by firing simultaneous requests without delays. Prevent them by applying full jitter to your exponential backoff strategy, which randomizes retry intervals and spaces out client requests efficiently.

Implement a cap on total elapsed time for HTTP retries by configuring maximum retry attempts alongside a total timeout threshold. This prevents endless loops and runaway requests during extended transient failures or strict rate limits.