The GIS account publishes parcel-change events that the public-works work-order system must consume, but today's synchronous HTTP calls fail when work-order is patching, causing missed tickets. Which integration pattern should architects introduce?
Select an answer to reveal the explanation.
Short Explanation
If GIS has to wait on hold for work-order, a patch night loses tickets. SNS shouts the parcel change; SQS holds the line until work-order is ready. That's a mailbox, not a stare-down.
Full Explanation
Amazon SNS and Amazon SQS provide pub/sub plus durable buffering between independently owned municipal systems, so GIS can publish parcel changes even when the work-order consumer is down. That decoupled integration is a core Task 4.4 pattern. Longer synchronous timeouts, overwrite-style S3 buses, and stopping GIS edits couple availability across accounts.