diff options
| author | Arn0 <yth@ythogtha.org> | 2022-03-08 20:19:41 +0100 |
|---|---|---|
| committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2022-03-09 09:36:27 +0700 |
| commit | 9a9964d19d161cf72df17316790e821f55056884 (patch) | |
| tree | 1ddc1fe54fd85562934b459f2f291d33c5ba0b67 /python/python3-celery/README | |
| parent | 9ce37db212d37691272b60a77554e8d7e9a97a18 (diff) | |
python/python3-celery: renamed from celery for python3, updated for version 5.2.3
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'python/python3-celery/README')
| -rw-r--r-- | python/python3-celery/README | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/python/python3-celery/README b/python/python3-celery/README new file mode 100644 index 0000000000..6bc0f28112 --- /dev/null +++ b/python/python3-celery/README @@ -0,0 +1,14 @@ +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. |