| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172 | .. _brokers:===================== Brokers=====================:Release: |version|:Date: |today|Celery supports several message transport alternatives... _broker_toc:Broker Instructions===================.. toctree::    :maxdepth: 1    rabbitmq    redis    sqlalchemy    django    mongodb    sqs    couchdb    beanstalk    ironmq.. _broker-overview:Broker Overview===============This is comparison table of the different transports supports,more information can be found in the documentation for eachindividual transport (see :ref:`broker_toc`).+---------------+--------------+----------------+--------------------+| **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 havededicated maintainers.Missing monitor support means that the transport does notimplement 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 workersat runtime using the `celery inspect` and `celery control` commands(and other tools using the remote control API).
 |