Resilience Patterns

APIs fail. Servers return 500s, rate limits trigger 429s, networks drop packets, TLS handshakes time out. Resilient automation anticipates these failures and handles them without human intervention.

What you will find here

Rate Limiting and Backoff: Every API enforces rate limits. Learn to read rate-limit headers, implement exponential backoff, and throttle pre-emptively to avoid hitting limits in the first place.
Retry Strategies: Not all errors deserve a retry. This page covers which errors to retry, how to add jitter to avoid thundering herds, circuit breaker patterns, and idempotency keys for safe retries on write operations.

Guiding principle

The difference between a script and automation is what happens when something goes wrong. A script fails and prints an error. Automation retries, backs off, and recovers — or fails with enough context to diagnose the problem without re-running.