Go HTTP Client Resilience

Treat HTTP as a failure-prone boundary with a finite time and resource budget. Retry only when both the failure and the operation are safe.

Core Workflow

1. Define operation semantics, total deadline, idempotency, and response limits.
2. Reuse a configured client and transport; propagate context into every request.
3. Construct URLs, headers, authentication, and bodies without secret leakage.
4. Classify transport, timeout, status, protocol, and decode failures.
5. Add bounded retries with jitter only for safe transient cases.
6. Drain or close bodies correctly and bound all reads.
7. Test with a function-backed transport and focused integration server.

Read Next