Snow-emergency service requests can spike suddenly against a city's intake API. Workers need time to process each request without dropping intake during the surge. Which decoupling pattern best fits?
Select an answer to reveal the explanation.
Short Explanation
SQS is the storm ticket hopper—citizens drop requests at the intake window, and workers pull tickets when they can. Making intake wait on every busy shovel crew is how the line spills into the street.
Full Explanation
Amazon SQS provides durable buffering between producers and consumers, which absorbs spikes and enables loosely coupled, asynchronous processing for surge workloads such as snow-emergency intake. Synchronous rejection under load, in-memory-only handoffs, and single-process tight coupling reintroduce scalability and reliability risks.