Publish-subscribe for broadcasting in RabbitMQ - Mini Project: Build & Apply

Publish-subscribe for broadcasting

📖 Scenario: You are setting up a simple messaging system where one sender can broadcast messages to multiple receivers. This is useful in real life when you want to send announcements or updates to many users at once.

🎯 Goal: Build a RabbitMQ publish-subscribe system using a fanout exchange to broadcast messages from one publisher to multiple subscribers.

📋 What You'll Learn

Create a fanout exchange named logs

Create two queues named queue1 and queue2

Bind both queues to the logs exchange

Publish a message 'Hello Subscribers!' to the logs exchange

Consume and print messages from both queues

💡 Why This Matters

🌍 Real World

Broadcasting messages is common in chat apps, live notifications, and event systems where many users need the same information at once.

💼 Career

Understanding publish-subscribe patterns and RabbitMQ is valuable for roles in DevOps, backend development, and system integration.

1

Setup the fanout exchange and queues

Create a fanout exchange called logs and two queues called queue1 and queue2 using the RabbitMQ Python client. Declare the exchange and queues so they exist on the server.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()
# Declare a fanout exchange named 'logs' and two queues named 'queue1' and 'queue2'
# Your code here

Hint

Use channel.exchange_declare with exchange_type='fanout' to create the exchange. Use channel.queue_declare to create each queue.

2

Bind the queues to the exchange

Bind the queues queue1 and queue2 to the logs exchange so they receive all messages published to it.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()

channel.exchange_declare(exchange='logs', exchange_type='fanout')
channel.queue_declare(queue='queue1')
channel.queue_declare(queue='queue2')
# Bind 'queue1' and 'queue2' to the 'logs' exchange
# Your code here

Hint

Use channel.queue_bind to connect each queue to the exchange.

3

Publish a message to the exchange

Publish the message 'Hello Subscribers!' to the logs exchange. Use an empty routing key since fanout exchanges ignore it.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()

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.queue_bind(exchange='logs', queue='queue2')
# Publish 'Hello Subscribers!' to the 'logs' exchange
# Your code here

Hint

Use channel.basic_publish with exchange='logs' and routing_key='' to send the message.

4

Consume and print messages from both queues

Consume one message from queue1 and one message from queue2. Print the message body from each queue to show that both received the broadcast.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()

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.queue_bind(exchange='logs', queue='queue2')

channel.basic_publish(exchange='logs', routing_key='', body='Hello Subscribers!')
# Consume one message from 'queue1' and 'queue2' and print their bodies
# Your code here

Hint

Use channel.basic_get with auto_ack=True to get one message from each queue. Decode the message body from bytes to string before printing.

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