AWS EventBridge
AWS serverless event bus connecting applications using events, enabling decoupled event-driven architectures with rule-based routing.
seed#aws#eventbridge#events#serverless#event-driven#integration
What it is
Amazon EventBridge is a serverless event bus that facilitates building event-driven architectures. It receives events from AWS sources, custom applications, and SaaS, routing them to targets based on content rules.
Key concepts
| Component | Function | Example |
|---|---|---|
| Event bus | Channel through which events flow | Default bus, custom bus per domain |
| Rules | Filters determining which events go to which targets | source: "orders" → Lambda |
| Targets | Event destinations | Lambda, SQS, Step Functions, API destinations |
| Schemas | Event structure | Auto-discovered or defined in Schema Registry |
| Pipes | Point-to-point connections with transformation | SQS → filter → enrichment → Lambda |
Patterns
- Fan-out: one event triggers multiple targets
- Event replay: re-process historical events
- Cross-account: events between AWS accounts
- Scheduled events: serverless cron jobs
- SaaS integration: events from Zendesk, Shopify, etc.
When to use EventBridge vs SQS/SNS
| Aspect | EventBridge | SQS/SNS |
|---|---|---|
| Routing | Content-based | Topic/queue |
| Schema | Integrated registry | No schema |
| SaaS | Native integrations | Manual |
| Cost | Per event | Per message |
Why it matters
EventBridge is the serverless event bus that connects AWS services, custom applications, and third-party SaaS. It enables building event-driven architectures without managing messaging infrastructure, with content-based event filtering and guaranteed delivery.
References
- EventBridge Documentation — Official documentation.
- EventBridge Event Patterns — AWS, 2024. Event filtering patterns.
- Serverless Land — EventBridge — AWS, 2024. Serverless patterns with EventBridge.