Event bus versus message queue for triggers
WHAT IT TESTS: messaging pattern selection. OUTLINE: a queue is point-to-point buffered work for one consumer group; an event bus routes and filters one event to many decoupled subscribers. Event bus wins when many independent services must react.
WHAT IT TESTS: whether you understand point-to-point queues versus publish-subscribe event routing. ANSWER OUTLINE: a message queue like SQS holds messages for one logical consumer to pull and process once, giving buffering, retries, and load leveling for a single workflow. An event bus like EventBridge publishes an event and routes copies to many subscribers based on content rules, decoupling producers from an unknown set of consumers. The event bus is clearly superior when one business event must fan out to several independent reactions.
Read the original → interview
- #eventbridge
- #sqs
- #event-driven
- #messaging
- #serverless
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.