Publish-subscribe for broadcasting in RabbitMQ - Commands & Configuration

Introduction

Sometimes you want to send the same message to many receivers at once. Publish-subscribe helps by letting one sender broadcast messages to multiple listeners easily.

When you want to send notifications to many services at the same time.

When multiple apps need to react to the same event, like a user signup.

When you want to separate message producers from consumers for better scaling.

When you want to add new listeners without changing the sender.

When you want to broadcast logs or metrics to different monitoring tools.

Config File - publish_subscribe_setup.sh

publish_subscribe_setup.sh

#!/bin/bash
# Create a fanout exchange for broadcasting
rabbitmqadmin declare exchange name=broadcast_exchange type=fanout

# Create queues for different consumers
rabbitmqadmin declare queue name=queue_1 durable=true
rabbitmqadmin declare queue name=queue_2 durable=true

# Bind queues to the exchange
rabbitmqadmin declare binding source=broadcast_exchange destination=queue_1
rabbitmqadmin declare binding source=broadcast_exchange destination=queue_2

This script sets up a fanout exchange named broadcast_exchange which broadcasts messages to all bound queues. It creates two durable queues queue_1 and queue_2. Then it binds both queues to the exchange so they receive all messages sent to it.

Commands

This command creates a fanout exchange named 'broadcast_exchange' which will broadcast messages to all queues bound to it.

Terminal

rabbitmqadmin declare exchange name=broadcast_exchange type=fanout

Expected Output

Successfully declared exchange 'broadcast_exchange'

→

name - Sets the name of the exchange

→

type - Defines the exchange type; 'fanout' broadcasts to all bound queues

Creates a durable queue named 'queue_1' that will receive broadcast messages.

Terminal

rabbitmqadmin declare queue name=queue_1 durable=true

Expected Output

Successfully declared queue 'queue_1'

→

name - Sets the queue name

→

durable - Makes the queue survive RabbitMQ restarts

Creates another durable queue named 'queue_2' for receiving broadcast messages.

Terminal

rabbitmqadmin declare queue name=queue_2 durable=true

Expected Output

Successfully declared queue 'queue_2'

→

name - Sets the queue name

→

durable - Makes the queue survive RabbitMQ restarts

Binds 'queue_1' to the 'broadcast_exchange' so it receives all messages sent to the exchange.

Terminal

rabbitmqadmin declare binding source=broadcast_exchange destination=queue_1

Expected Output

Successfully declared binding from 'broadcast_exchange' to 'queue_1'

→

source - The exchange name

→

destination - The queue name to bind

Binds 'queue_2' to the 'broadcast_exchange' so it also receives all broadcast messages.

Terminal

rabbitmqadmin declare binding source=broadcast_exchange destination=queue_2

Expected Output

Successfully declared binding from 'broadcast_exchange' to 'queue_2'

→

source - The exchange name

→

destination - The queue name to bind

Key Concept

If you remember nothing else from this pattern, remember: a fanout exchange sends every message to all queues bound to it, enabling easy broadcasting.

Common Mistakes

Using a direct or topic exchange instead of fanout for broadcasting

Direct and topic exchanges route messages based on keys, so not all queues get the message.

Use a fanout exchange to broadcast messages to all bound queues regardless of routing keys.

Not binding queues to the exchange after creating them

Queues won't receive any messages if they are not bound to the exchange.

Always bind each queue to the fanout exchange to receive broadcast messages.

Creating non-durable queues without understanding persistence needs

Non-durable queues disappear after RabbitMQ restarts, losing messages.

Set queues as durable if you want them to survive server restarts.

Summary

Create a fanout exchange to broadcast messages to multiple queues.

Create durable queues that will receive the broadcast messages.

Bind each queue to the fanout exchange to ensure they get all messages.

Practice

1. What is the main purpose of using a fanout exchange in RabbitMQ's publish-subscribe pattern?

easy

A. To broadcast messages to all queues bound to the exchange

B. To route messages to a single queue based on a key

C. To store messages until a consumer is ready

D. To filter messages based on content

Solution

1. Step 1: Understand fanout exchange behavior

   A fanout exchange sends messages to all queues bound to it without filtering or routing keys.

2. Step 2: Compare with other exchange types

   Other exchanges like direct or topic route messages selectively, but fanout broadcasts to all.

3. Final Answer:

   To broadcast messages to all queues bound to the exchange -> Option A

4. Quick Check:

   Fanout = Broadcast all [OK]

Hint: Fanout means send to all queues bound [OK]

Common Mistakes:

• Confusing fanout with direct exchange routing
• Thinking fanout filters messages
• Assuming fanout stores messages

2. Which of the following is the correct RabbitMQ command to declare a fanout exchange named logs?

easy

A. rabbitmqadmin declare exchange name=logs type=direct

B. rabbitmqadmin declare exchange name=logs type=fanout

C. rabbitmqadmin declare queue name=logs

D. rabbitmqadmin declare exchange name=logs type=topic

Solution

1. Step 1: Identify the correct exchange type for broadcasting

   The fanout type is used for broadcasting messages to all bound queues.

2. Step 2: Check the command syntax

   The command uses rabbitmqadmin declare exchange with name=logs and type=fanout to declare the exchange.

3. Final Answer:

   rabbitmqadmin declare exchange name=logs type=fanout -> Option B

4. Quick Check:

   Fanout exchange declaration = rabbitmqadmin declare exchange name=logs type=fanout [OK]

Hint: Fanout exchange uses type=fanout in declare command [OK]

Common Mistakes:

• Using direct or topic instead of fanout
• Declaring a queue instead of an exchange
• Incorrect command syntax

3. Given the following setup:

channel.exchange_declare(exchange='logs', exchange_type='fanout')
channel.queue_declare(queue='queue1')
channel.queue_bind(exchange='logs', queue='queue1')
channel.basic_publish(exchange='logs', routing_key='', body='Hello')

What will happen when the message is published?

medium

A. The message is sent to a default queue

B. The message is sent only to 'queue1' because of the routing key

C. The message is sent to all queues bound to 'logs', including 'queue1'

D. The message is discarded because routing_key is empty

Solution

1. Step 1: Understand fanout exchange behavior

   Fanout exchange ignores routing keys and sends messages to all bound queues.

2. Step 2: Analyze the code bindings

   Queue 'queue1' is bound to 'logs' exchange, so it will receive the message.

3. Final Answer:

   The message is sent to all queues bound to 'logs', including 'queue1' -> Option C

4. Quick Check:

   Fanout ignores routing key, sends to all bound queues [OK]

Hint: Fanout ignores routing_key, sends to all bound queues [OK]

Common Mistakes:

• Thinking routing_key matters for fanout
• Assuming message is discarded if routing_key is empty
• Believing message goes to default queue

4. You wrote this code to broadcast messages but only one queue receives them:

channel.exchange_declare(exchange='logs', exchange_type='fanout')
channel.queue_declare(queue='queue1')
channel.queue_declare(queue='queue2')
channel.queue_bind(exchange='logs', queue='queue1')
channel.basic_publish(exchange='logs', routing_key='', body='Test')

What is the likely problem?

medium

A. Queue 'queue2' is not bound to the exchange

B. The exchange type should be 'direct' instead of 'fanout'

C. The routing_key is missing

D. The queues are declared incorrectly

Solution

1. Step 1: Check queue bindings

   Only 'queue1' is bound to the 'logs' exchange; 'queue2' is not bound.

2. Step 2: Understand fanout behavior

   Fanout sends messages to all bound queues, so unbound queues won't get messages.

3. Final Answer:

   Queue 'queue2' is not bound to the exchange -> Option A

4. Quick Check:

   All queues must be bound to receive messages [OK]

Hint: Bind all queues to exchange to receive broadcasts [OK]

Common Mistakes:

• Assuming routing_key is needed for fanout
• Changing exchange type unnecessarily
• Not binding all queues

5. You want to broadcast logs to multiple services dynamically. Which approach best ensures each service gets its own queue and receives all messages without interfering with others?

hard

A. Services publish messages directly to each other's queues

B. All services share a single queue bound to a direct exchange

C. Each service creates a queue bound to a topic exchange with different routing keys

D. Each service creates a unique queue and binds it to a shared fanout exchange

Solution

1. Step 1: Understand publish-subscribe pattern

   Fanout exchange broadcasts messages to all bound queues, ideal for multiple receivers.

2. Step 2: Ensure isolation and dynamic addition

   Each service having its own queue bound to the fanout exchange ensures independent consumption and easy scaling.

3. Step 3: Evaluate other options

   Sharing a single queue causes message competition; topic exchange with routing keys is more selective, not broadcast; direct publishing is complex and error-prone.

4. Final Answer:

   Each service creates a unique queue and binds it to a shared fanout exchange -> Option D

5. Quick Check:

   Fanout + unique queues = broadcast to all [OK]

Hint: Use fanout exchange with unique queues per service [OK]

Common Mistakes:

• Using a single shared queue causing message loss
• Confusing topic exchange for broadcast
• Direct publishing to queues instead of exchange