Direct exchange in RabbitMQ - Commands & Configuration

Introduction

A direct exchange in RabbitMQ routes messages to queues based on an exact matching routing key. It helps deliver messages precisely to the intended queue without confusion.

When you want to send a message to a specific queue identified by a unique key.

When you have multiple queues and want to control exactly which queue receives which message.

When you need simple routing without complex pattern matching.

When building a task queue where each task type has its own queue.

When you want to ensure messages do not get broadcasted to unintended queues.

Config File - direct_exchange_setup.sh

direct_exchange_setup.sh

#!/bin/bash

# Declare a direct exchange named 'my_direct_exchange'
curl -i -u guest:guest -H "content-type:application/json" \
  -XPUT \
  -d '{"type":"direct"}' \
  http://localhost:15672/api/exchanges/%2f/my_direct_exchange

# Declare a queue named 'task_queue'
curl -i -u guest:guest -H "content-type:application/json" \
  -XPUT \
  -d '{}' \
  http://localhost:15672/api/queues/%2f/task_queue

# Bind the queue to the exchange with routing key 'task_key'
curl -i -u guest:guest -H "content-type:application/json" \
  -XPOST \
  -d '{"routing_key":"task_key"}' \
  http://localhost:15672/api/bindings/%2f/e/my_direct_exchange/q/task_queue

This script creates a direct exchange called my_direct_exchange. It then creates a queue named task_queue. Finally, it binds the queue to the exchange using the routing key task_key. Messages sent to the exchange with this key will go to task_queue.

Commands

This command creates a direct exchange named 'my_direct_exchange' where messages will be routed based on exact routing keys.

Terminal

rabbitmqadmin declare exchange name=my_direct_exchange type=direct

Expected Output

Successfully declared exchange 'my_direct_exchange'

→

name - Specifies the name of the exchange to create

→

type - Sets the exchange type to direct for exact routing

This command creates a durable queue named 'task_queue' that will receive messages routed by the exchange.

Terminal

rabbitmqadmin declare queue name=task_queue durable=true

Expected Output

Successfully declared queue 'task_queue'

→

name - Specifies the queue name

→

durable - Makes the queue survive server restarts

This command binds the 'task_queue' to the 'my_direct_exchange' exchange with the routing key 'task_key'. Messages with this key go to this queue.

Terminal

rabbitmqadmin declare binding source=my_direct_exchange destination=task_queue destination_type=queue routing_key=task_key

Expected Output

Successfully declared binding from 'my_direct_exchange' to 'task_queue' with routing key 'task_key'

→

source - The exchange name

→

destination - The queue name

→

destination_type - Specifies that the destination is a queue

→

routing_key - The exact key used for routing messages

This command sends a message with the routing key 'task_key' to the direct exchange. It will be delivered to 'task_queue'.

Terminal

rabbitmqadmin publish exchange=my_direct_exchange routing_key=task_key payload='Hello Direct Exchange!'

Expected Output

Message published

→

exchange - Specifies which exchange to send the message to

→

routing_key - The routing key to match the queue binding

→

payload - The message content

This command retrieves the message from 'task_queue' to verify it was routed correctly.

Terminal

rabbitmqadmin get queue=task_queue requeue=false

Expected Output

Message count: 0

Payload: Hello Direct Exchange!

→

queue - Specifies the queue to get messages from

→

requeue - Whether to put the message back after getting it; false means remove it

Key Concept

If you remember nothing else from this pattern, remember: a direct exchange routes messages only to queues whose binding key exactly matches the message's routing key.

Common Mistakes

Using a routing key in the message that does not exactly match any queue binding key.

The message will not be delivered to any queue and will be lost or dropped.

Always ensure the routing key in the message matches exactly one of the queue binding keys.

Binding a queue to the exchange without specifying a routing key.

The binding will not work as expected because direct exchanges require routing keys for matching.

Always specify a routing key when binding a queue to a direct exchange.

Publishing messages to the wrong exchange type or name.

Messages will not be routed correctly and may be lost.

Double-check the exchange name and type before publishing messages.

Summary

Create a direct exchange to route messages by exact routing keys.

Declare queues and bind them to the exchange with specific routing keys.

Publish messages with routing keys to deliver them to the correct queue.

Retrieve messages from the queue to verify correct routing.

Practice

1. What is the main behavior of a direct exchange in RabbitMQ?

easy

A. It broadcasts messages to all queues regardless of routing keys.

B. It routes messages based on pattern matching of routing keys.

C. It routes messages to queues with an exact matching routing key.

D. It stores messages without routing them to any queue.

Solution

1. Step 1: Understand direct exchange routing

   A direct exchange routes messages only to queues whose binding key exactly matches the message's routing key.

2. Step 2: Compare with other exchange types

   Unlike fanout (broadcast) or topic (pattern matching) exchanges, direct exchange requires exact key match.

3. Final Answer:

   It routes messages to queues with an exact matching routing key. -> Option C

4. Quick Check:

   Direct exchange = exact routing key match [OK]

Hint: Direct exchange matches routing keys exactly [OK]

Common Mistakes:

• Confusing direct with fanout exchange behavior
• Thinking direct exchange uses pattern matching
• Assuming messages go to all queues regardless of keys

2. Which of the following is the correct way to declare a direct exchange named logs_direct using RabbitMQ's command line tool rabbitmqadmin?

easy

A. rabbitmqadmin add exchange logs_direct type=fanout

B. rabbitmqadmin declare exchange name=logs_direct type=direct

C. rabbitmqadmin create exchange logs_direct direct

D. rabbitmqadmin declare exchange logs_direct type=topic

Solution

1. Step 1: Recall rabbitmqadmin syntax for exchange declaration

   The correct syntax is: rabbitmqadmin declare exchange name=EXCHANGE_NAME type=EXCHANGE_TYPE

2. Step 2: Match the command to declare a direct exchange named logs_direct

   rabbitmqadmin declare exchange name=logs_direct type=direct matches the syntax and specifies type=direct correctly.

3. Final Answer:

   rabbitmqadmin declare exchange name=logs_direct type=direct -> Option B

4. Quick Check:

   rabbitmqadmin declare exchange + name + type=direct [OK]

Hint: Use 'declare exchange name=... type=direct' syntax [OK]

Common Mistakes:

• Using 'create' instead of 'declare'
• Wrong exchange type like fanout or topic
• Missing 'name=' before exchange name

3. Given a direct exchange ex_direct with two queues bound: queue1 with routing key info and queue2 with routing key error. If a message is published with routing key info, which queues will receive the message?

medium

A. Only queue1

B. Only queue2

C. Both queue1 and queue2

D. No queue receives the message

Solution

1. Step 1: Identify bindings and routing keys

   queue1 is bound with routing key 'info', queue2 with 'error'. The message has routing key 'info'.

2. Step 2: Apply direct exchange routing rule

   Direct exchange routes messages only to queues with exact matching routing keys. So only queue1 matches.

3. Final Answer:

   Only queue1 -> Option A

4. Quick Check:

   Message routing key = queue binding key [OK]

Hint: Message goes only to queues with exact routing key match [OK]

Common Mistakes:

• Assuming message goes to all queues
• Confusing routing keys with patterns
• Thinking queue2 also receives message

4. You declared a direct exchange and bound a queue with routing key task. However, messages published with routing key tasks are not received by the queue. What is the most likely cause?

medium

A. Message payload is empty

B. Exchange type is incorrectly set to fanout

C. Queue is not declared properly

D. Routing key mismatch between binding and message

Solution

1. Step 1: Check routing key binding and message key

   The queue is bound with routing key 'task' but messages are sent with 'tasks'. These keys differ.

2. Step 2: Understand direct exchange routing behavior

   Direct exchange requires exact routing key match. A mismatch means the message won't be routed to the queue.

3. Final Answer:

   Routing key mismatch between binding and message -> Option D

4. Quick Check:

   Exact routing key match needed [OK]

Hint: Check routing keys for exact spelling match [OK]

Common Mistakes:

• Assuming fanout exchange routes by keys
• Blaming queue declaration without checking keys
• Thinking empty payload blocks routing

5. You have a direct exchange ex_direct with three queues bound: Q1 with routing key red, Q2 with routing key blue, and Q3 with routing key red. If you publish a message with routing key red, which queues receive the message and why?

hard

A. Q1 and Q3 both receive it because they share the same routing key

B. No queue receives it because multiple bindings cause conflict

C. Only Q3 receives it because it was bound last

D. Only Q1 receives it because it was bound first

Solution

1. Step 1: Identify queues bound with routing key 'red'

   Q1 and Q3 are both bound with routing key 'red'. Q2 is bound with 'blue'.

2. Step 2: Apply direct exchange routing logic

   Direct exchange routes messages to all queues with matching routing keys. So both Q1 and Q3 receive the message.

3. Final Answer:

   Q1 and Q3 both receive it because they share the same routing key -> Option A

4. Quick Check:

   Multiple queues with same key all get message [OK]

Hint: Multiple queues with same key all get messages [OK]

Common Mistakes:

• Thinking only one queue receives the message
• Assuming binding order affects routing
• Believing multiple bindings cause conflicts