Installation Brokers Using RabbitMQ Using Redis Using SQLAlchemy Using the Django Database Using MongoDB Using CouchDB Using Beanstalk First steps with Celery Choosing your Broker Creating a simple task Redis [http://code.google.com/p/redis/], Beanstalk [http://kr.github.com/beanstalkd/], MongoDB [http://mongodb.org/], CouchDB [http://couchdb.apache.org/] and databases (using SQLAlchemy [http://www the result 8 Simple! Features Messaging Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when using

Installation Brokers Using RabbitMQ Using Redis Using SQLAlchemy Using the Django Database Using MongoDB Using CouchDB Using Beanstalk First steps with Celery Choosing your Broker Creating a simple task RabbitMQ [http://www.rabbitmq.com/], but support for Redis [http://code.google.com/p/redis/], MongoDB [http://mongodb.org/], Beanstalk [http://kr.github.com/beanstalkd/], Amazon SQS [http://aws.amazon.com/sqs/] the result 8 Simple! Features Messaging Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when using

webhooks. The recommended message broker is RabbitMQ, but limited support for Redis, Beanstalk, MongoDB, CouchDB and databases (using SQLAlchemy or the Django ORM) is also available. Celery is easy to Release 2.4.7 1.1.3 Features Mes- saging Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault- tolerant Excellent configurable error recovery when backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Web- hooks Your tasks can also

producers, autoscalers, broker transports and much more. It supports Brokers RabbitMQ, Redis, MongoDB (exp), ZeroMQ (exp) CouchDB (exp), SQLAlchemy (exp) Django ORM (exp), Amazon SQS, (exp) and more… (multiprocessing), Eventlet, gevent threads/single threaded Result Stores AMQP, Redis memcached, MongoDB SQLAlchemy, Django ORM Apache Cassandra Serialization pickle, json, yaml, msgpack. zlib, bzip2 celery[redis]: for using Redis as a message transport or as a result backend. celery[mongodb]: for using MongoDB as a message transport (experimental), or as a result backend (supported). celery[sqs]:

backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Webhooks Your tasks can also be HTTP callbacks, enabling AMQP backend settings Cache backend settings Tokyo Tyrant backend settings Redis backend settings MongoDB backend settings Message Routing Broker Settings Task execution settings Worker: celeryd Error E-Mails [http://memcached.org] to store the results. See Cache backend settings. mongodb Use MongoDB [http://mongodb.org] to store the results. See MongoDB backend settings. redis Use Redis [http://code.google.com/p/redis/]

for Redis [http://code.google.com/p/redis/], Beanstalk [http://kr.github.com/beanstalkd/], MongoDB [http://mongodb.org/], CouchDB [http://couchdb.apache.org/] and databases (using SQLAlchemy [http://www.sqlalchemy the result 8 Simple! Features Messaging Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your tasks can also be

producers, autoscalers, broker transports and much more. It supports • Brokers • RabbitMQ, Redis, • MongoDB (exp), ZeroMQ (exp) • CouchDB (exp), SQLAlchemy (exp) • Django ORM (exp), Amazon SQS, (exp) • and Documentation, Release 3.1.25 • threads/single threaded • Result Stores • AMQP, Redis • memcached, MongoDB • SQLAlchemy, Django ORM • Apache Cassandra • Serialization • pickle, json, yaml, msgpack. • zlib celery[redis] for using Redis as a message transport or as a result backend. celery[mongodb] for using MongoDB as a message transport (experimental), or as a result backend (supported). celery[sqs]

Redis [http://code.google.com/p/redis/], Beanstalk [http://kr.github.com/beanstalkd/], MongoDB [http://mongodb.org/], CouchDB [http://couchdb.apache.org/] and databases (using SQLAlchemy [http://www the result 8 Simple! Features Messaging Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your tasks can also be

integration PaaS compatible with multiple instances Multi cluster monitor Redis, Disque, IronMQ, SQS, MongoDB or ORM Rollbar support Django Q is tested with: Python 2.7 & 3.6. Django 1.8.18 LTS, 1.10.7 and broker_class bulk poll cache cached scheduler rollbar cpu_affinity Brokers Redis Disque IronMQ Amazon SQS MongoDB Django ORM Custom Broker Reference Tasks async() Async Cached operations Synchronous testing Connection IronMQ broker: $ pip install iron-mq Pymongo [https://github.com/mongodb/mongo-python-driver] is needed if you want to use MongoDB as a message broker: $ pip install pymongo Redis [http://redis.io/]

language, and a PHP client. The recommended message broker is RabbitMQ, but support for Redis, MongoDB, Beanstalk, Amazon SQS, CouchDB and databases (using SQLAlchemy or the Django ORM) is also available Release 2.5.5 1.1.4 Features Mes- saging Supported brokers include RabbitMQ, Redis, Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault- tolerant Excellent configurable error recovery when backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Cassandra, or AMQP (message notification). Web- hooks Your tasks can also be HTTP callbacks