aboutsummaryrefslogtreecommitdiff
path: root/python/celery/README
diff options
context:
space:
mode:
authorYth - Arnaud <yth@ythogtha.org>2019-10-26 18:43:45 +0700
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2019-10-26 18:52:03 +0700
commitd90dcde49f4f672fe41e216aa6d4b07a7883f724 (patch)
treec28eb082b500a9a6e4536ef421e558e1b4c1b7fe /python/celery/README
parenta405b5a2c4fb625eccad6c745833a267ecc55a9f (diff)
python/celery: Added (Distributed Task Queue).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'python/celery/README')
-rw-r--r--python/celery/README13
1 files changed, 13 insertions, 0 deletions
diff --git a/python/celery/README b/python/celery/README
new file mode 100644
index 0000000000000..afa76c63dbbc8
--- /dev/null
+++ b/python/celery/README
@@ -0,0 +1,13 @@
+Distributed 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.