Message Queues
In depthConcept
Also known as: Berichtenwachtrijen
Messages are placed in a queue and processed by consumers, decoupling the systems involved.
Message Queues, explained
Written by EduVerseWhat it is
A message queue is a buffer between parts of a system. A producer puts a message on the queue, for example “order 123 was placed”, and one or more consumers pick it up and process it when they’re ready. RabbitMQ, Amazon SQS and Kafka are well-known tools in this area.
Why teams use it
The sender doesn’t have to wait for the receiver, or even know who it is. If the consumer is slow or down for a while, messages simply wait in the queue instead of getting lost. That lets teams scale and deploy services separately and absorb sudden peaks in traffic.
An example from work
Your order service publishes a message after every purchase, and a separate worker sends the confirmation email. When the mail provider is down for an hour, customers notice nothing. In the RabbitMQ management screen you watch the queue grow to a few hundred messages, then drain once the provider is back.
Our own explanation, not a quote from the book.
Where it fits
Asynchronous communication, decoupling services
Coverage in the book
Covered in depth: multiple pages with explanations, examples and simulations.
