EventBridge
Definition
AWS serverless event bus service for connecting applications using events. Like a central message router that delivers events to the right destinations.
Use Cases
- Amazon: Decoupling microservices in an e-commerce workflow (order placed -> downstream processing). — Services publish domain events (for example, OrderCreated) to an event bus. EventBridge rules route matching events to multiple targets such as AWS Lambda for orchestration, Amazon SQS for buffering, and AWS Step Functions for long-running workflows. Dead-letter queues and retries handle failures without blocking the producer. (Looser coupling between teams and services, easier fan-out to new consumers, and more resilient processing because downstream failures don’t stop order intake.)
- Netflix: Event-driven automation for cloud operations (for example, reacting to infrastructure and application events). — Operational events are emitted and routed to automated handlers. In AWS-centric setups, this pattern is commonly implemented by routing events to compute (such as Lambda) and workflow engines (such as Step Functions) for remediation and notifications, with filtering rules to reduce noise. (Faster incident response and more consistent operational actions through automation triggered by events rather than manual intervention.)
Provider Equivalents
- AWS: Amazon EventBridge
- Azure: Azure Event Grid
- GCP: Eventarc
- OCI: OCI Events Service
Frequently Asked Questions
- What's the difference between EventBridge and SNS?
- SNS is primarily a pub/sub messaging service for pushing messages to subscribers (topics) with simple filtering. EventBridge is an event router: it matches structured events against rules (often using event patterns) and can route to many AWS service targets, supports multiple event sources (AWS services, custom apps, and many SaaS partners), and includes features like schema discovery/registry. Use SNS when you mainly need message fan-out; use EventBridge when you need event-based routing and integration across services.
- When should I use EventBridge?
- Use EventBridge when you want to connect services using events without tight coupling—especially for microservices, audit/monitoring pipelines, and workflows like “order placed” triggering inventory, billing, and shipping. It’s a good fit when you need rule-based filtering, multiple targets, and easy integration with AWS services (Lambda, Step Functions, SQS, Kinesis, API destinations). If you need high-throughput streaming analytics, consider Kinesis; if you need point-to-point task queues, consider SQS.
- How much does EventBridge cost?
- EventBridge pricing is mainly based on the number of events published/ingested and additional features you use (for example, some advanced capabilities like event replay/archiving, schema features, or cross-account/cross-region patterns may add cost depending on configuration). You also pay for downstream targets you invoke (Lambda, Step Functions, SQS, etc.). For accurate numbers, check the current AWS EventBridge pricing page and estimate monthly event volume and rule/target usage.
Category: communication
Difficulty: intermediate
Related Terms
See Also