introduction.txt 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203
  1. :Version: 4.0.0rc2 (0today8)
  2. :Web: http://celeryproject.org/
  3. :Download: http://pypi.python.org/pypi/celery/
  4. :Source: https://github.com/celery/celery/
  5. :Keywords: task queue, job queue, asynchronous, async, rabbitmq, amqp, redis,
  6. python, webhooks, queue, distributed
  7. --
  8. What is a Task Queue?
  9. =====================
  10. Task queues are used as a mechanism to distribute work across threads or
  11. machines.
  12. A task queue's input is a unit of work, called a task, dedicated worker
  13. processes then constantly monitor the queue for new work to perform.
  14. Celery communicates via messages, usually using a broker
  15. to mediate between clients and workers. To initiate a task a client puts a
  16. message on the queue, the broker then delivers the message to a worker.
  17. A Celery system can consist of multiple workers and brokers, giving way
  18. to high availability and horizontal scaling.
  19. Celery is written in Python, but the protocol can be implemented in any
  20. language. In addition to Python there's node-celery_ for Node.js,
  21. and a `PHP client`_.
  22. Language interoperability can also be achieved
  23. by `using webhooks`_.
  24. .. _node-celery: https://github.com/mher/node-celery
  25. .. _`PHP client`: https://github.com/gjedeer/celery-php
  26. .. _`using webhooks`:
  27. http://docs.celeryproject.org/en/latest/userguide/remote-tasks.html
  28. What do I need?
  29. ===============
  30. Celery version 4.0 runs on,
  31. - Python (2.7, 3.4, 3.5)
  32. - PyPy (5.1, 2.4)
  33. This is the last version to support Python 2.7,
  34. and from the next version (Celery 5.x) Python 3.6 or newer is required.
  35. If you are running an older version of Python, you need to be running
  36. an older version of Celery:
  37. - Python 2.6: Celery series 3.1 or earlier.
  38. - Python 2.5: Celery series 3.0 or earlier.
  39. - Python 2.4 was Celery series 2.2 or earlier.
  40. Celery is a project with minimal funding,
  41. so we do not support Microsoft Windows.
  42. Please do not open any issues related to that platform.
  43. *Celery* is usually used with a message broker to send and receive messages.
  44. The RabbitMQ transports is feature complete, but there's also Qpid and Amazon
  45. SQS broker support.
  46. *Celery* can run on a single machine, on multiple machines, or even
  47. across datacenters.
  48. Get Started
  49. ===========
  50. If this is the first time you're trying to use Celery, or you are
  51. new to Celery 4.0 coming from previous versions then you should read our
  52. getting started tutorials:
  53. - `First steps with Celery`_
  54. Tutorial teaching you the bare minimum needed to get started with Celery.
  55. - `Next steps`_
  56. A more complete overview, showing more features.
  57. .. _`First steps with Celery`:
  58. http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html
  59. .. _`Next steps`:
  60. http://docs.celeryproject.org/en/latest/getting-started/next-steps.html
  61. Celery is…
  62. ==========
  63. - **Simple**
  64. Celery is easy to use and maintain, and does *not need configuration files*.
  65. It has an active, friendly community you can talk to for support,
  66. including a `mailing-list`_ and and an IRC channel.
  67. Here's one of the simplest applications you can make::
  68. from celery import Celery
  69. app = Celery('hello', broker='amqp://guest@localhost//')
  70. @app.task
  71. def hello():
  72. return 'hello world'
  73. - **Highly Available**
  74. Workers and clients will automatically retry in the event
  75. of connection loss or failure, and some brokers support
  76. HA in way of *Master/Master* or *Master/Slave* replication.
  77. - **Fast**
  78. A single Celery process can process millions of tasks a minute,
  79. with sub-millisecond round-trip latency (using RabbitMQ,
  80. py-librabbitmq, and optimized settings).
  81. - **Flexible**
  82. Almost every part of *Celery* can be extended or used on its own,
  83. Custom pool implementations, serializers, compression schemes, logging,
  84. schedulers, consumers, producers, broker transports and much more.
  85. It supports…
  86. ============
  87. - **Message Transports**
  88. - RabbitMQ_, Amazon SQS
  89. - **Concurrency**
  90. - Prefork, Eventlet_, gevent_, single threaded (``solo``)
  91. - **Result Stores**
  92. - AMQP, Redis
  93. - memcached
  94. - SQLAlchemy, Django ORM
  95. - Apache Cassandra, IronCache, Elasticsearch
  96. - **Serialization**
  97. - *pickle*, *json*, *yaml*, *msgpack*.
  98. - *zlib*, *bzip2* compression.
  99. - Cryptographic message signing.
  100. .. _`Eventlet`: http://eventlet.net/
  101. .. _`gevent`: http://gevent.org/
  102. .. _RabbitMQ: http://rabbitmq.com
  103. .. _Redis: http://redis.io
  104. .. _SQLAlchemy: http://sqlalchemy.org
  105. Framework Integration
  106. =====================
  107. Celery is easy to integrate with web frameworks, some of which even have
  108. integration packages:
  109. +--------------------+------------------------+
  110. | `Django`_ | not needed |
  111. +--------------------+------------------------+
  112. | `Pyramid`_ | `pyramid_celery`_ |
  113. +--------------------+------------------------+
  114. | `Pylons`_ | `celery-pylons`_ |
  115. +--------------------+------------------------+
  116. | `Flask`_ | not needed |
  117. +--------------------+------------------------+
  118. | `web2py`_ | `web2py-celery`_ |
  119. +--------------------+------------------------+
  120. | `Tornado`_ | `tornado-celery`_ |
  121. +--------------------+------------------------+
  122. The integration packages are not strictly necessary, but they can make
  123. development easier, and sometimes they add important hooks like closing
  124. database connections at ``fork``.
  125. .. _`Django`: http://djangoproject.com/
  126. .. _`Pylons`: http://pylonsproject.org/
  127. .. _`Flask`: http://flask.pocoo.org/
  128. .. _`web2py`: http://web2py.com/
  129. .. _`Bottle`: http://bottlepy.org/
  130. .. _`Pyramid`: http://docs.pylonsproject.org/en/latest/docs/pyramid.html
  131. .. _`pyramid_celery`: http://pypi.python.org/pypi/pyramid_celery/
  132. .. _`django-celery`: http://pypi.python.org/pypi/django-celery
  133. .. _`celery-pylons`: http://pypi.python.org/pypi/celery-pylons
  134. .. _`web2py-celery`: http://code.google.com/p/web2py-celery/
  135. .. _`Tornado`: http://www.tornadoweb.org/
  136. .. _`tornado-celery`: https://github.com/mher/tornado-celery/
  137. .. _celery-documentation:
  138. Documentation
  139. =============
  140. The `latest documentation`_ with user guides, tutorials and API reference
  141. is hosted at Read The Docs.
  142. .. _`latest documentation`: http://docs.celeryproject.org/en/latest/