Five parallel workers in the city's UCS inventory poller each retry as if they alone owned the entire API rate ceiling and still trip 429. What robust pattern should they use?
Select an answer to reveal the explanation.
Short Explanation
Five clerks each assuming they own the whole ticket roll will empty it together. One shared pacekeeper—or a single paced queue—keeps the team under the ceiling.
Full Explanation
When parallel workers ignore a shared rate budget, they trip 429 even if a single client would not. Robust handling uses a process-wide limiter or paced queue across outbound calls. Per-thread ignorance of the same limit, hour-long timeouts, or abandoning parallelism altogether miss the shared-pacing lesson.