Why RabbitMQ?
Why message brokers decouple services, and how exchanges, queues, acknowledgements and competing consumers work.
Transcript
Services that call each other directly are tightly coupled: if one is down, the caller suffers.
A message broker sits in the middle, so producers and consumers do not need to be online together.
In RabbitMQ, a producer publishes to an exchange, which routes messages into queues using bindings.
Consumers take messages from a queue and send an acknowledgement. Unacknowledged messages are delivered again.
Several consumers on one queue share the work, which is how you scale out.
RabbitMQ is a great fit for background jobs, flexible routing, and request and reply.
Decouple the work. Deliver it reliably.
