An icon for a calendar

Published June 14, 2022

RabbitMQ Topic vs Direct exchange

Rabbitmq Topic vs Direct exchange

1. Overview

In this article, we will learn the differences between RabbitMQ Topic vs Direct exchange. To learn more about other RabbitMQ topics, refer to these articles.

2. RabbitMQ Topic vs Direct Exchange

Direct Topic
A direct exchange delivers messages to queues based on the message routing key. Topic exchanges route messages to one or many queues based on matching between a message routing key and the pattern that was
used to bind a queue to an exchange.
Can’t behave like other exchanges Can behave like other exchanges
Does not support # or * wildcard characters Supports special characters “*” and “#”
Can’t behave like a topic exchange When special characters “*” (star) and “#” (hash) aren’t used in bindings, the topic exchange will behave just like a direct one.
You can bind multiple queues with the same binding key.
In that case, the direct exchange will behave like fanout and will broadcast the message to all the matching queues.
When a queue is bound with “#” (hash) binding key – it will receive all the messages, regardless of the routing key – like in fanout exchange.
It can’t do routing based on multiple criteria. It can route based on multiple criteria
RabbitMQ Direct vs Topic exchange

See this article to understand the terminologies Queue, Exchange, Routing and binding keys.

3. RabbitMQ Direct exchange

In direct exchange, a message goes to the queues whose binding key exactly matches the routing key of the message.

A direct exchange is ideal for the Unicast routing (one-to-one) of messages (although we can use it for multi cast – one-to-many routing as well).

Here is how it works:

  • A queue binds to the exchange with a routing key K
  • When a new message with routing key R arrives at the direct exchange, the exchange routes it to the queue if K = R

3.1. Work queues

We can use the Work Queue to distribute time-consuming tasks among multiple workers or consumers.

In this way, you can avoid doing a resource-intensive task immediately and having to wait for it to complete. Instead, we schedule the task to be done later. We encapsulate a task as a message and send it to a queue. A worker process running in the background will pop the tasks and eventually execute the job.

This concept is especially useful in web applications, where it’s impossible to handle a complex task during a short HTTP request window.

The RabbitMQ can share the tasks with multiple workers.

3.1.1. Direct exchange with work queues

Direct exchanges are often used to distribute tasks between multiple workers or consumers (instances of the same application) in a round-robin manner.

It load balance the messages between consumers and not between queues.

The RabbitMQ will send each message to the next consumer, in sequence. On average, every consumer will get the same number of messages. This way of distributing messages is called round-robin. 

Look at the following block. We have two workers listening for messages. RabbitMQ delivers each message sequentially. Worker 1 gets the first message and then worker 2 gets the second message. Again, worker 1 gets the third message and worker 2 gets the fourth message. The same process repeats.

This article originally appeared on, to read the full article, click here.

Start Optimizing Your Integration Infrastructure with meshIQ!