topics / async-messaging
Message Queue
A generic event-driven pipeline, not one broker's API — a bounded backlog, competing or fanned-out consumers, and what actually happens when one crashes mid-job or the producer outruns them. Switch delivery modes, kill a consumer, and watch redelivery, retries and the dead-letter queue do their jobs.
New here? Hover any underlined word for a quick definition, orstart with Study →
0published
0acked
0retried
0dead-lettered
0dropped (backpressure)
Consumers
C0
idle, waiting for work
0 processed0 failed
C1
idle, waiting for work
0 processed0 failed
C2
idle, waiting for work
0 processed0 failed
Event log
Waiting for traffic…
Delivery mode
One shared backlog — each message is delivered to exactly one consumer, whichever is free first.
Broker config
backpressure, once the backlog is full
Traffic