Clients submitting long-running records requests need a fast acknowledgment while work continues asynchronously. Which edge pattern best fits?
Select an answer to reveal the explanation.
Short Explanation
Take a ticket at the counter—API Gateway drops work on SQS and hands back a fast “we’ve got it,” while the shop works in the back. Making citizens wait hours on an open HTTP call is the opposite of loose coupling.
Full Explanation
API Gateway can integrate with SQS to acknowledge requests quickly (commonly with asynchronous acceptance semantics) while downstream consumers process work. Holding synchronous connections for long jobs couples clients to backend duration and harms scalability.