AMQP, RabbitMQ and Celery - A Visual Guide For Dummies

AMQP, RabbitMQ and Celery - A Visual Guide For Dummies

Citation Copied

Work in Progress

Celery is an asynchronous distributed task queue. RabbitMQ is a message broker which implements the Advanced Message Queuing Protocol (AMQP). Before we describe relationship between RabbitMQ and Celery, a quick overview of AMQP will be helpful [1][2].

Amqp Key Terms

Message Or Task

A message or task consists of attributes (headers) and payload (body). Some attributes are used by broker but most are used by consumers. Optional attributes are known as headers. Some common attributes are

  1. Content type
  2. Content encoding
  3. Routing key

Massage payload or body contains data that goes to the consumer. Normally a serialisation format such as JSON is used for message payload. Content type and content encoding attributes are used to communicate the serialisation format. An example message payload serialised in JSON looks like,

	"task": "myapp.tasks.add",
	"id": "54086c5e-6193-4575-8308-dbab76798756",
	"args": [4, 4],
	"kwargs": {}


A producer is a user application that sends messages.


A broker receives messages from producer and router them to consume. A broker consists an exchange and one or more queues.


A producer can send messages to queues only via exchange. Exchanges take a message from producer and route it into zero or more queues. The routing algorithm used depends on the exchange type and rules called bindings.


A message or task queue is a buffer that stores messages.


Bindings are rules that the exchange uses to route messages to queues.

Routing Keys

Bindings may have an optional routing key attribute. An exchange may use this field to route a message to the bound queue.

Celery and RabbitMQ


A consumer is an application that receives messages and process them.


Celery generally hides the complexity of AMQP protocols [3]. Celery act as both the producer and consumer of RabbitMQ messages. In Celery, the producer is called client or publisher and consumers are called as workers. It is possible to use a different custom consumer (worker) or producer (client).

RabbitMQ or AMQP message queues are basically task queues.


Message originates from a Celery client. The message body [4] contains

  • name of the task to execute,
  • task id (UUID)
  • arguments to execute task with
  • additional metadata – like the retries, eta, expires.

An example Celery message,

{"id": "4cc7438e-afd4-4f8f-a2f3-f46567e7ca77",
 "task": "celery.task.PingTask",
 "args": [],
 "kwargs": {},
 "retries": 0,
 "eta": "2009-11-17T12:30:56.527191"


RabbitMQ route messages/tasks to one or more queues. Routing of tasks requires:

  1. Defining queues using CELERY_QUEUES setting. CELERY_QUEUES is a map of queue names and their exchange/exchange_type/binding_key.

  2. Specifying task destination. The destination for a task is decided by the following (in order)

    a. The Routers defined in CELERY_ROUTES setting. CELERY_ROUTES is a map of task names and their queue/routing_key.

    b. The routing arguments to Task.apply_async().

    c. Routing related attributes defined in the Task itself.

In the AMQP both routing_key and binding_key are referred as the routing key.


The exchange type defines how the messages are routed through the exchange. The exchange types defined in the standard are direct, topic, fanout and headers.


The relationship between exchanges and a queue is called a binding.


Normally one server will have one node, but you can run multiple nodes on the same server.

Each node has multiple worker processes or threads. By default multiprocessing is used to perform concurrent execution of tasks.

The number of worker processes/threads can be changed using the --concurrency argument and defaults to the number of CPUs available on the machine.


Various messaging scenarios are supported between Node to taskQueue -1:M, M:M, M:1, 1:1, Round-robin etc.

Producer, Broker, Consumer Arrangements

As AMQP is a network protocol, the producers, consumers and the broker can all reside on the same or different machines. Following are the possible arrangements for producer, broker and consumer,

Celery and RabbitMQ- Producer-Broker-Consumer Arrangements

  1. AMQP in 10 mins ↩︎

  2. AMQP Concepts ↩︎

  3. AMQP Primer ↩︎

  4. Celery Messages ↩︎

Abhishek Tiwari

Abhishek Tiwari

Tech Savant, Servant Leader

View Comments
Next Post

CloudFront Design Patterns And Best Practices

Previous Post

Going Static

Subscribe to Abhishek Tiwari

Subscribe to our newsletter and receive access to exclusive posts and content updates. We don't spam and your email won't be shared with third-parties.

Thanks for subscribing!

Check your inbox to confirm your subscription.

Please enter a valid email address!