This document describes the current stable version of Celery (3.1). For development docs, go here.


Date:May 26, 2014

Celery supports several message transport alternatives.

Broker Instructions

Broker Overview

This is comparison table of the different transports supports, more information can be found in the documentation for each individual transport (see Broker Instructions).

Name Status Monitoring Remote Control
RabbitMQ Stable Yes Yes
Redis Stable Yes Yes
Mongo DB Experimental Yes Yes
Beanstalk Experimental No No
Amazon SQS Experimental No No
Couch DB Experimental No No
Zookeeper Experimental No No
Django DB Experimental No No
SQLAlchemy Experimental No No
Iron MQ 3rd party No No

Experimental brokers may be functional but they do not have dedicated maintainers.

Missing monitor support means that the transport does not implement events, and as such Flower, celery events, celerymon and other event-based monitoring tools will not work.

Remote control means the ability to inspect and manage workers at runtime using the celery inspect and celery control commands (and other tools using the remote control API).

Previous topic

Introduction to Celery

Next topic

Using RabbitMQ

This Page