introduction.txt 6.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202
  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 3.0 runs on,
  31. - Python (2.7, 3.4, 3.5)
  32. - PyPy (1.8, 1.9)
  33. - Jython (2.5, 2.7).
  34. This is the last version to support Python 2.5,
  35. and from Celery 3.1, Python 2.6 or later is required.
  36. The last version to support Python 2.4 was Celery series 2.2.
  37. *Celery* is usually used with a message broker to send and receive messages.
  38. The RabbitMQ, Redis transports are feature complete,
  39. but there's also experimental support for a myriad of other solutions, including
  40. using SQLite for local development.
  41. *Celery* can run on a single machine, on multiple machines, or even
  42. across datacenters.
  43. Get Started
  44. ===========
  45. If this is the first time you're trying to use Celery, or you are
  46. new to Celery 3.0 coming from previous versions then you should read our
  47. getting started tutorials:
  48. - `First steps with Celery`_
  49. Tutorial teaching you the bare minimum needed to get started with Celery.
  50. - `Next steps`_
  51. A more complete overview, showing more features.
  52. .. _`First steps with Celery`:
  53. http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html
  54. .. _`Next steps`:
  55. http://docs.celeryproject.org/en/latest/getting-started/next-steps.html
  56. Celery is…
  57. ==========
  58. - **Simple**
  59. Celery is easy to use and maintain, and does *not need configuration files*.
  60. It has an active, friendly community you can talk to for support,
  61. including a `mailing-list`_ and and an IRC channel.
  62. Here's one of the simplest applications you can make::
  63. from celery import Celery
  64. app = Celery('hello', broker='amqp://guest@localhost//')
  65. @app.task
  66. def hello():
  67. return 'hello world'
  68. - **Highly Available**
  69. Workers and clients will automatically retry in the event
  70. of connection loss or failure, and some brokers support
  71. HA in way of *Master/Master* or *Master/Slave* replication.
  72. - **Fast**
  73. A single Celery process can process millions of tasks a minute,
  74. with sub-millisecond round-trip latency (using RabbitMQ,
  75. py-librabbitmq, and optimized settings).
  76. - **Flexible**
  77. Almost every part of *Celery* can be extended or used on its own,
  78. Custom pool implementations, serializers, compression schemes, logging,
  79. schedulers, consumers, producers, autoscalers, broker transports and much more.
  80. It supports…
  81. ============
  82. - **Message Transports**
  83. - RabbitMQ_, Redis_,
  84. - MongoDB_ (experimental), Amazon SQS (experimental),
  85. - CouchDB_ (experimental), SQLAlchemy_ (experimental),
  86. - Django ORM (experimental), `IronMQ`_
  87. - and more…
  88. - **Concurrency**
  89. - Prefork, Eventlet_, gevent_, threads/single threaded
  90. - **Result Stores**
  91. - AMQP, Redis
  92. - memcached, MongoDB
  93. - SQLAlchemy, Django ORM
  94. - Apache Cassandra, IronCache, Elasticsearch
  95. - **Serialization**
  96. - *pickle*, *json*, *yaml*, *msgpack*.
  97. - *zlib*, *bzip2* compression.
  98. - Cryptographic message signing.
  99. .. _`Eventlet`: http://eventlet.net/
  100. .. _`gevent`: http://gevent.org/
  101. .. _RabbitMQ: http://rabbitmq.com
  102. .. _Redis: http://redis.io
  103. .. _MongoDB: http://mongodb.org
  104. .. _Beanstalk: http://kr.github.com/beanstalkd
  105. .. _CouchDB: http://couchdb.apache.org
  106. .. _SQLAlchemy: http://sqlalchemy.org
  107. .. _`IronMQ`: http://iron.io
  108. Framework Integration
  109. =====================
  110. Celery is easy to integrate with web frameworks, some of which even have
  111. integration packages:
  112. +--------------------+------------------------+
  113. | `Django`_ | not needed |
  114. +--------------------+------------------------+
  115. | `Pyramid`_ | `pyramid_celery`_ |
  116. +--------------------+------------------------+
  117. | `Pylons`_ | `celery-pylons`_ |
  118. +--------------------+------------------------+
  119. | `Flask`_ | not needed |
  120. +--------------------+------------------------+
  121. | `web2py`_ | `web2py-celery`_ |
  122. +--------------------+------------------------+
  123. | `Tornado`_ | `tornado-celery`_ |
  124. +--------------------+------------------------+
  125. The integration packages are not strictly necessary, but they can make
  126. development easier, and sometimes they add important hooks like closing
  127. database connections at ``fork``.
  128. .. _`Django`: http://djangoproject.com/
  129. .. _`Pylons`: http://pylonsproject.org/
  130. .. _`Flask`: http://flask.pocoo.org/
  131. .. _`web2py`: http://web2py.com/
  132. .. _`Bottle`: http://bottlepy.org/
  133. .. _`Pyramid`: http://docs.pylonsproject.org/en/latest/docs/pyramid.html
  134. .. _`pyramid_celery`: http://pypi.python.org/pypi/pyramid_celery/
  135. .. _`django-celery`: http://pypi.python.org/pypi/django-celery
  136. .. _`celery-pylons`: http://pypi.python.org/pypi/celery-pylons
  137. .. _`web2py-celery`: http://code.google.com/p/web2py-celery/
  138. .. _`Tornado`: http://www.tornadoweb.org/
  139. .. _`tornado-celery`: https://github.com/mher/tornado-celery/
  140. .. _celery-documentation:
  141. Documentation
  142. =============
  143. The `latest documentation`_ with user guides, tutorials and API reference
  144. is hosted at Read The Docs.
  145. .. _`latest documentation`: http://docs.celeryproject.org/en/latest/