A city's vital-records print shop falls behind when peak online orders hit printers synchronously from the web tier. Which change best loosens coupling and absorbs the spike?
Select an answer to reveal the explanation.
Short Explanation
Think of the print shop like a take-a-number deli, not a phone that rings until someone picks up. Drop each order on an SQS queue so the web tier can finish the citizen's click while workers chew through spikes at their own pace. Synchronous sockets, bigger thread pools, and raw NFS shares still glue the web tier to printer speed.
Full Explanation
Amazon SQS is the standard loose-coupling buffer between producers and consumers: the web tier enqueues print jobs and returns quickly while workers poll or are triggered as capacity allows. That absorbs order spikes without tying HTTP request lifetime to printer hardware. Long-lived blocking sockets, larger synchronous thread pools, and direct NFS writes keep the web tier tightly coupled to printer throughput and failure modes.