- Published:
- Last updated:
Messaging and Event-Driven Architecture
- Authors
- Name
- Lucian Oprea
- @LucianDSA_
00:30:00
Filter by difficulty
30 of 30 questions shown
Communication Models and Topology
⏷ 1. When should a system use asynchronous messaging instead of synchronous request-response?
⏷ 2. What is the difference between a message queue and an append-only log?
⏷ 3. How do point-to-point, publish-subscribe, and fan-out messaging differ?
⏷ 4. How do routing keys, topics, and subscriptions control message delivery?
⏷ 5. What ordering guarantees can a messaging system provide, and how do you choose an ordering key?
Delivery and Consumer Correctness
Free preview complete
You’ve reached the end of the free preview
Get every remaining question and complete answer, plus progress tracking across the full Interview Question Library.
- 25 more questions and complete answers in this topic
- Full access to every interview topic
- Progress tracking and question flags
- New questions and improvements during your subscription
Full access from
$12/month
No long-term commitment. Cancel whenever you want.
⏷ 6. How do at-most-once, at-least-once, and effectively-once processing differ?
⏷ 7. How do you design an idempotent message consumer?
⏷ 8. How do acknowledgements, visibility timeouts, and offset commits handle consumer failure?
⏷ 9. How should message retries, dead-letter queues, and poison messages be handled?
⏷ 10. How do consumer groups scale processing, and what happens during rebalancing?
Backpressure and Operational Safety
⏷ 11. How do you handle backpressure and a growing message backlog?
Consistency, Evolution, and Replay
⏷ 12. What is the dual-write problem, and how do the transactional outbox and CDC address it?
⏷ 13. How do sagas coordinate a workflow across services?
⏷ 14. How do you evolve event schemas without breaking consumers?
⏷ 15. How do you replay events safely?
Messaging Essentials
⏷ 16. What are producers, brokers, and consumers in a messaging system?
⏷ 17. How do events and commands differ?
⏷ 18. What is a message backlog?
⏷ 19. What does acknowledging a message mean?
⏷ 20. What is a dead-letter queue?
⏷ 21. What makes a message durable?
Delivery Design and Operations
⏷ 22. How should message keys and partitions be chosen?
⏷ 23. How would you implement delayed or scheduled messages?
⏷ 24. When are priority queues appropriate?
⏷ 25. How do you bound message deduplication state?
⏷ 26. Which metrics show whether a message consumer is healthy?
Large-Scale Event Architecture
⏷ 27. How would you design cross-region messaging?
⏷ 28. What do broker transactions guarantee, and what do they not guarantee?
⏷ 29. How do you govern event contracts across teams?
⏷ 30. How do you migrate from one broker or topic topology to another?