SQS vs SNS vs EventBridge — which messaging service for which job?
⚡ Short Answer
SQS = a queue (one consumer group pulls, decouples + buffers work). SNS = pub/sub fan-out (push one message to many subscribers). EventBridge = event bus with content-based routing rules, schema registry, and SaaS/AWS event integrations. Pattern: SNS/EventBridge fan-out → SQS per consumer.
☕Coffee Chat Question
Concept Made Simple
“SQS vs SNS vs EventBridge — which messaging service for which job?”
🧠Mind Map Answer
Remember It Faster
🔥What If?
Think Beyond the Expected
Why is the 'SNS → SQS' fan-out pattern so common?
SNS pushes each event to multiple subscribers, but push delivery can drop if a consumer is down. Subscribing an SQS queue per consumer buffers events durably so each consumer processes at its own pace with retries/DLQ — combining fan-out with reliable, decoupled consumption.
😂Real World
SNS→SQS fan-out and EventBridge routing are the backbone of event-driven AWS; picking SQS vs SNS vs EventBridge by fan-out/routing/buffering needs is a routine design decision.
🎯Interviewer's Expectation
Keywords they're listening for:
⚠️Common Mistakes
- ✗SNS-only fan-out without SQS buffering
- ✗Using SQS where you need fan-out
- ✗Ignoring FIFO/ordering needs
✅Best Practices
- ✓SNS/EventBridge fan-out → SQS per consumer
- ✓Add DLQs for poison messages
- ✓EventBridge for content-based routing
🔁Follow-up Questions
- 1SQS standard vs FIFO?
- 2When EventBridge over SNS?
- 3How does a DLQ fit in?
🧩Related Technologies
Continue Learning with AI
Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.
Plain-language foundations
I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner. Topic: Lambda (AWS) Interview question: "SQS vs SNS vs EventBridge — which messaging service for which job?" Please: 1. Explain the core idea in simple, plain language, using an everyday analogy. 2. Define any technical terms you use. 3. Walk through one small, concrete example. 4. Finish with a single sentence I can easily remember. Keep the tone friendly and assume I'm new to this topic.
Was this answer helpful?
⭐ Featured Products
Support our platform by exploring our recommended products.
As an Amazon affiliate, purchases through these links may earn us a small commission — at no extra cost to you. It helps keep Full Stack Interview Guru free.