Understanding Direct, Fanout, and Topic Exchange Modes in RabbitMQ

Direct Mode (Direct)

We first look at the flowchart of the Direct mode.

The producer sends a message without specifying an exchange name, only a routing key (KEY). RabbitMQ therefore treats the message as using Direct mode.

In Direct mode the exchange exists but does not affect routing; the message is placed directly into the queue whose name matches the routing key.

The limitation of Direct mode is that it can only deliver to a single queue (point‑to‑point).

One‑sentence summary: Use this mode when the message needs to be sent to a unique node.

If you need a message to be received by multiple queues, you must use one of the following patterns.

Fanout Mode (Fanout)

First, examine the flowchart of the Fanout mode.

Here the message includes an exchange name, indicating that the message should be handled by that exchange. To use Fanout mode, set the exchange type to fanout as shown in the following diagram.

Binding three queues to this exchange (as illustrated) allows a single message to be delivered to all bound queues.

One‑sentence summary: Use this mode when you need to broadcast a message to multiple queues.

However, this approach can feel rigid; you may want finer control over which queues receive a particular message without creating many exchanges.

The enhanced version of Fanout, known as the Topic mode, is introduced next.

Topic Mode (Topic)

First, look at the flowchart of the Topic mode.

Each queue has a binding key. The red‑lined examples show that a binding key like usa.# performs a wildcard match: any routing key that starts with usa. will be routed to that queue.

One‑sentence summary: Any message sent to a Topic exchange is forwarded to all queues whose binding keys match the routing key, providing flexible and powerful routing capabilities.

Thank you for reading, hope this helps :) Source: blog.csdn.net/z806899669/article/details/89063713