What messaging scenarios are supported by AMQP and RabbitMQ?
AMQP is a very general system that can be configured to cover a great variety of messaging middleware use-cases. For example: • Point-to-point communication One of the simplest and most common scenarios is for a message producer to transmit a message addressed to a particular message consumer. AMQP covers this scenario by allowing queues to be named and to be bound to a “direct” exchange, which routes messages to queues by name. • One-to-many broadcasting (including multicast) In this scenario, the broadcasters publish messages to an AMQP “fanout” exchange, and subscribers create and subscribe to their own private AMQP queues, which forward published messages on to them, with one copy per queue. Multicast is addressed at the broker implementation level. AMQP clients need not be made aware of transport-level optimisations such as multicast: broker clusters are free to use whatever such low-level optimisations are available from configuration to configuration. Multiple optimisations are
