Ravi Sir's Cards › AWS
EventBridge vs SNS/SQS
This revision card explains EventBridge vs SNS/SQS. It starts from the need that teams often pick the first messaging service they know and paint themselves into a corner. It describes SNS — fan-out notifications. SQS: durable queue for one consumer group. EventBridge: rich content filters, many AWS targets, SaaS partners. The how-to section covers how to use EventBridge when you need pattern matching across services; use SQS when one worker pool must not lose jobs. An example on the card is orderPlaced to analytics + fraud + email: EventBridge rules. Payment worker pool: SQS.
Read card text
What this card says
Why do we need it?
Teams often pick the first messaging service they know and paint themselves into a corner.
What is it?
SNS: fan-out notifications. SQS: durable queue for one consumer group. EventBridge: rich content filters, many AWS targets, SaaS partners.
How to do it
Use EventBridge when you need pattern matching across services; use SQS when one worker pool must not lose jobs.
content filter
Example
OrderPlaced to analytics + fraud + email: EventBridge rules. Payment worker pool: SQS.