Use case

This module provides a connection to an AMQP-compatible Message Queue server (such as RabbitMQ).

IBM has a decent explanation of what a Message Queue can be used for:

Queuing is the mechanism by which messages are held until an application is ready to process them. Queuing allows you to:

• Communicate between programs (which might each be running in different environments) without having to write the communication code.
• Select the order in which a program processes messages.
• Balance loads on a system by arranging for more than one program to service a queue when the number of messages exceeds a threshold.
• Increase the availability of your applications by arranging for an alternative system to service the queues if your primary system is unavailable.

In our organization, we are using this module to publish and consume messages to and from our corporate message queue server. Various publishers and consumers are configured to listen to that server and perform a variety of tasks such as logging, copying large files, notifications, publishing, and other events.

This is similar to, but different from, an event server; which is responsible for telling the clients (consumers) what to do. A message queue server is responsible for sending a message from a publisher to connected consumer(s); and the consumer decides what to do with that message. This approach allows us to define different consumers which perform different actions (sometimes on the same message).

I hope that helps explain further; let me know if you needed further information.

Thank you,
-dellintosh