api-rate-limiters

Handle API rate limits by applying exponential backoff and a circuit breaker decorator to external API calls, which pauses requests and prevents cascading failures when blocks are detected.

You detect API blocks by scanning HTTP status codes like 403 and rate-limit headers such as X-Rate-Limit-Remaining, then raising a structured WorkerError to stop execution.

Yes, you can use SQLite-based TTL caching with configurable windows like 15 minutes or 6 hours to store dynamic data and reduce duplicate API calls during offline scenarios.

The best way to test API rate limiting without mocks is to enforce the breaker decorator on real external connections and verify that structured WorkerErrors are raised upon block detection.

Your external API connection raises a WorkerError because the circuit breaker detects rate limit exhaustion via headers or 403 responses and proactively terminates the process to ensure resilience.