PDF generation for permit packets must not block the citizen API. How should the architect decouple and scale the workers?
Select an answer to reveal the explanation.
Short Explanation
Park the heavy PDF press on a side street: the API drops a ticket on SQS and workers clock in when the queue grows. Cranking the API box bigger still ties citizens to the printing press.
Full Explanation
Decoupling CPU-heavy work uses a queue such as Amazon SQS so the API acknowledges quickly while workers scale on queue depth. Vertical upsizing of the API alone keeps coupling and latency risk. Client-only or browser-storage approaches are not durable municipal processing designs.