This document describes Celery 3.1. For development docs, go here.
|Date:||December 04, 2013|
Celery supports several message transport alternatives.
This is comparison table of the different transports supports, more information can be found in the documentation for each individual transport (see Broker Instructions).
|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).