AWS
Microservices
intermediate
Event-Driven Microservices — AWS Architecture Template
Services publish domain events to EventBridge, which fans out through per-consumer SQS queues to independent handlers.
Why this architecture works
- EventBridge decouples producers from consumers — new subscribers are added with rules, not code changes
- A queue per consumer buffers bursts and lets each service process at its own pace
- SQS in front of every handler provides retries and dead-lettering instead of lost events
- Mixing Lambda and Fargate consumers matches compute to workload: spiky vs long-running
- Idempotent handlers keyed on event IDs in DynamoDB make at-least-once delivery safe
What's inside (9 resources)
API Ingress
aws-api-gateway
Producer Service
aws-ecs
Event Bus
aws-eventbridge
Billing Queue
aws-sqs
Shipping Queue
aws-sqs
Billing Handler
aws-lambda
Shipping Service
aws-fargate
State Store
aws-dynamodb
Event Metrics
aws-cloudwatch
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform or CloudFormation in one click.
- Review the plan diff and security scan, then deploy with human approval.