A courts calendar sync calls a vendor API that returns intermittent…

Question

A courts calendar sync calls a vendor API that returns intermittent HTTP 503s. Naive immediate retries stampede the vendor. What retry strategy should application code implement?

Accepted Answer

Implement exponential backoff (ideally with jitter) so retry spacing grows after transient 503s. — Hammering a sick vendor with instant retries is like honking in a traffic jam — it makes the jam worse. Back off longer each try, preferably with jitter. Transient 503s deserve patience, not a stampede.

Answer

Retry as fast as the CPU allows with zero delay between attempts.

Answer

Retry once immediately, then disable the feature for thirty days.

Answer

Treat every 503 as a permanent failure and never retry.

A courts calendar sync calls a vendor API that returns intermittent HTTP 503s. Naive immediate retries stampede the vendor. What retry strategy should application code implement?

Short Explanation

Full Explanation