AWS Async Job Queue with SQS
About This Architecture
Asynchronous job-processing pattern on AWS: a client posts work to API Gateway, a Lambda function enqueues it onto an SQS job queue and instantly returns a job ID, while a separate ECS/Fargate worker pool consumes the queue, processes each job, and writes progress to a DynamoDB status table; the client either polls the status endpoint or receives a WebSocket push, and jobs that repeatedly fail land in a dead-letter queue.
Architecture prompt
Asynchronous job-processing pattern on AWS: a client posts work to API Gateway, a Lambda function enqueues it onto an SQS job queue and instantly returns a job ID, while a separate ECS/Fargate worker pool consumes the queue, processes each job, and writes progress to a DynamoDB status table; the client either polls the status endpoint or receives a WebSocket push, and jobs that repeatedly fail land in a dead-letter queue.
Generated by Diagrams.so — AI architecture diagram generator with native Draw.io output. Fork this diagram, remix it, or download as .drawio, PNG, or SVG.
