A city records portal accepts citizen uploads on an API tier and must virus-scan files with a separate worker fleet. How should the architect enable each tier to scale independently under load?
Select an answer to reveal the explanation.
Short Explanation
Don’t chain the front desk to the back-room scanner with the same rope. Park upload messages on SQS so the API and scan workers scale on their own clocks. One process, instance-store queues, or a global mutex turns spikes into a traffic jam.
Full Explanation
Loose coupling with Amazon SQS allows the upload API and virus-scan workers to scale independently based on their own demand and processing rates. Embedding scan work in the API process, using ephemeral local disks as queues, or serializing all work with a mutex prevents independent elasticity and hurts high-performing compute design under civic upload spikes.