123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201 |
- :Version: 4.2.0rc3 (latentcall)
- :Web: http://celeryproject.org/
- :Download: https://pypi.org/project/celery/
- :Source: https://github.com/celery/celery/
- :Keywords: task, queue, job, async, rabbitmq, amqp, redis,
- python, distributed, actors
- --
- What's a Task Queue?
- ====================
- Task queues are used as a mechanism to distribute work across threads or
- machines.
- A task queue's input is a unit of work, called a task, dedicated worker
- processes then constantly monitor the queue for new work to perform.
- Celery communicates via messages, usually using a broker
- to mediate between clients and workers. To initiate a task a client puts a
- message on the queue, the broker then delivers the message to a worker.
- A Celery system can consist of multiple workers and brokers, giving way
- to high availability and horizontal scaling.
- Celery is written in Python, but the protocol can be implemented in any
- language. In addition to Python there's node-celery_ for Node.js,
- and a `PHP client`_.
- Language interoperability can also be achieved by using webhooks
- in such a way that the client enqueues an URL to be requested by a worker.
- .. _node-celery: https://github.com/mher/node-celery
- .. _`PHP client`: https://github.com/gjedeer/celery-php
- What do I need?
- ===============
- Celery version 4.0 runs on,
- - Python (2.7, 3.4, 3.5)
- - PyPy (5.4, 5.5)
- This is the last version to support Python 2.7,
- and from the next version (Celery 5.x) Python 3.5 or newer is required.
- If you're running an older version of Python, you need to be running
- an older version of Celery:
- - Python 2.6: Celery series 3.1 or earlier.
- - Python 2.5: Celery series 3.0 or earlier.
- - Python 2.4 was Celery series 2.2 or earlier.
- Celery is a project with minimal funding,
- so we don't support Microsoft Windows.
- Please don't open any issues related to that platform.
- *Celery* is usually used with a message broker to send and receive messages.
- The RabbitMQ, Redis transports are feature complete,
- but there's also experimental support for a myriad of other solutions, including
- using SQLite for local development.
- *Celery* can run on a single machine, on multiple machines, or even
- across datacenters.
- Get Started
- ===========
- If this is the first time you're trying to use Celery, or you're
- new to Celery 4.0 coming from previous versions then you should read our
- getting started tutorials:
- - `First steps with Celery`_
- Tutorial teaching you the bare minimum needed to get started with Celery.
- - `Next steps`_
- A more complete overview, showing more features.
- .. _`First steps with Celery`:
- http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html
- .. _`Next steps`:
- http://docs.celeryproject.org/en/latest/getting-started/next-steps.html
- Celery is…
- =============
- - **Simple**
- Celery is easy to use and maintain, and does *not need configuration files*.
- It has an active, friendly community you can talk to for support,
- like at our `mailing-list`_, or the IRC channel.
- Here's one of the simplest applications you can make::
- from celery import Celery
- app = Celery('hello', broker='amqp://guest@localhost//')
- @app.task
- def hello():
- return 'hello world'
- - **Highly Available**
- Workers and clients will automatically retry in the event
- of connection loss or failure, and some brokers support
- HA in way of *Primary/Primary* or *Primary/Replica* replication.
- - **Fast**
- A single Celery process can process millions of tasks a minute,
- with sub-millisecond round-trip latency (using RabbitMQ,
- py-librabbitmq, and optimized settings).
- - **Flexible**
- Almost every part of *Celery* can be extended or used on its own,
- Custom pool implementations, serializers, compression schemes, logging,
- schedulers, consumers, producers, broker transports, and much more.
- It supports…
- ================
- - **Message Transports**
- - RabbitMQ_, Redis_, Amazon SQS
- - **Concurrency**
- - Prefork, Eventlet_, gevent_, single threaded (``solo``)
- - **Result Stores**
- - AMQP, Redis
- - memcached
- - SQLAlchemy, Django ORM
- - Apache Cassandra, IronCache, Elasticsearch
- - **Serialization**
- - *pickle*, *json*, *yaml*, *msgpack*.
- - *zlib*, *bzip2* compression.
- - Cryptographic message signing.
- .. _`Eventlet`: http://eventlet.net/
- .. _`gevent`: http://gevent.org/
- .. _RabbitMQ: https://rabbitmq.com
- .. _Redis: https://redis.io
- .. _SQLAlchemy: http://sqlalchemy.org
- Framework Integration
- =====================
- Celery is easy to integrate with web frameworks, some of which even have
- integration packages:
- +--------------------+------------------------+
- | `Django`_ | not needed |
- +--------------------+------------------------+
- | `Pyramid`_ | `pyramid_celery`_ |
- +--------------------+------------------------+
- | `Pylons`_ | `celery-pylons`_ |
- +--------------------+------------------------+
- | `Flask`_ | not needed |
- +--------------------+------------------------+
- | `web2py`_ | `web2py-celery`_ |
- +--------------------+------------------------+
- | `Tornado`_ | `tornado-celery`_ |
- +--------------------+------------------------+
- The integration packages aren't strictly necessary, but they can make
- development easier, and sometimes they add important hooks like closing
- database connections at ``fork``.
- .. _`Django`: https://djangoproject.com/
- .. _`Pylons`: http://pylonsproject.org/
- .. _`Flask`: http://flask.pocoo.org/
- .. _`web2py`: http://web2py.com/
- .. _`Bottle`: https://bottlepy.org/
- .. _`Pyramid`: http://docs.pylonsproject.org/en/latest/docs/pyramid.html
- .. _`pyramid_celery`: https://pypi.org/project/pyramid_celery/
- .. _`celery-pylons`: https://pypi.org/project/celery-pylons/
- .. _`web2py-celery`: https://code.google.com/p/web2py-celery/
- .. _`Tornado`: http://www.tornadoweb.org/
- .. _`tornado-celery`: https://github.com/mher/tornado-celery/
- .. _celery-documentation:
- Documentation
- =============
- The `latest documentation`_ is hosted at Read The Docs, containing user guides,
- tutorials, and an API reference.
- .. _`latest documentation`: http://docs.celeryproject.org/en/latest/
|