Consuming messages in RabbitMQ - Commands & Configuration

Introduction

When you send messages to a queue, you need a way to receive and process them. Consuming messages means reading these messages from the queue so your application can use the information or trigger actions.

When you want your app to react to new orders placed in an online store.

When you need to process tasks like sending emails after users sign up.

When you want to handle logs or events from different parts of your system asynchronously.

When you want to balance work between multiple workers by distributing messages.

When you want to ensure messages are processed reliably even if your app restarts.

Commands

This command creates a durable queue named 'my-queue' where messages will be stored until consumed.

Terminal

rabbitmqadmin declare queue name=my-queue durable=true

Expected Output

Successfully declared queue 'my-queue'

→

name - Sets the name of the queue

→

durable - Makes the queue survive RabbitMQ restarts

This sends a message with the text 'Hello, RabbitMQ!' to the 'my-queue' queue.

Terminal

rabbitmqadmin publish routing_key=my-queue payload='Hello, RabbitMQ!'

Expected Output

Published message to queue 'my-queue'

→

routing_key - Specifies the queue to send the message to

→

payload - The content of the message

This command consumes (retrieves) one message from 'my-queue' and removes it from the queue so it won't be processed again.

Terminal

rabbitmqadmin get queue=my-queue requeue=false

Expected Output

Message count: 0

Payload: Hello, RabbitMQ!

→

queue - Specifies which queue to consume from

→

requeue - false means the message is removed after consumption

Key Concept

If you remember nothing else from this pattern, remember: consuming messages means reading and removing them from the queue so your app can process them once.

Common Mistakes

Consuming messages without acknowledging or removing them

Messages stay in the queue and get delivered repeatedly, causing duplicate processing.

Use commands or client code that acknowledges messages or sets requeue=false to remove them after processing.

Trying to consume from a queue that does not exist

The command or client will fail because the queue is missing.

Always declare or verify the queue exists before consuming messages.

Publishing messages to the wrong routing key or exchange

Messages never reach the intended queue and are lost or stuck.

Double-check routing keys and exchange bindings to ensure messages go to the correct queue.

Summary

Declare a durable queue to hold messages safely.

Publish messages to the queue using the correct routing key.

Consume messages from the queue and remove them to avoid duplicates.