A city permit API spikes when storm season opens, overwhelming workers that process applications synchronously. How should the architect loosely couple intake from processing so each tier can scale independently?
Select an answer to reveal the explanation.
Short Explanation
When the storm permit line explodes, do not make the clerk and the back office share one heartbeat. Drop requests on SQS so the API keeps accepting while workers chew through the pile at their own pace. One fat box still sync-calling is a traffic jam with a bigger engine.
Full Explanation
Amazon SQS buffers work between producers and consumers, enabling independent scaling of the permit intake API and processing fleet. Synchronous in-request processing, vertical scale alone, or pushing load back to citizens does not provide the same loose coupling for spike absorption.