AWS · Event-Driven
Async Fan-Out Event Processing
API Gateway triggering SNS Topic fan-out to parallel SQS Queues for Email workers and Analytics S3 Data Lake. This diagram is written in ArchLex and passes AWS provider checks.
Diagram and source
provider aws
direction LR
apigw: api-gateway
publisher: lambda
topic: sns
queue_email: sqs
worker_email: lambda
queue_analytics: sqs
worker_analytics: lambda
data_lake: s3
apigw > publisher > topic
topic -[publishes]->|fan-out| queue_email > worker_email
topic -[publishes]->|fan-out| queue_analytics > worker_analytics > data_lakeWhat is in this diagram.
Resources
- apigw Amazon API Gateway
- publisher AWS Lambda
- topic Amazon SNS
- queue_email Amazon SQS
- worker_email AWS Lambda
- queue_analytics Amazon SQS
- worker_analytics AWS Lambda
- data_lake Amazon S3
Relationships
- apigw connects publisher
- publisher connects topic
- topic publishes queue_email
- queue_email connects worker_email
- topic publishes queue_analytics
- queue_analytics connects worker_analytics
- worker_analytics connects data_lake
Render it yourself.
Save the source as async-fanout-messaging.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.
npx @archlex/cli render async-fanout-messaging.arch --output async-fanout-messaging.svgRelated examples.
- Event-Driven MicroservicesEventBridge publishing to SQS Queue subscribed by Lambda
- Minimal Vertical SliceRDS Proxy, RDS Database, and ECS Service
- Display Labels & Named InstancesInstance names and custom display labels distinguishing primary and replica databases
- Classic 3-Tier Web ArchitectureApplication Load Balancer distributing to ECS container tasks connected to RDS