From 096d59f38dd5465c4deb7a64bccd2816ba77a9ca Mon Sep 17 00:00:00 2001 From: Marc Aymerich Date: Thu, 7 May 2015 19:50:37 +0000 Subject: [PATCH] Added README on tasks contrib application0 --- orchestra/contrib/tasks/README.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 orchestra/contrib/tasks/README.md diff --git a/orchestra/contrib/tasks/README.md b/orchestra/contrib/tasks/README.md new file mode 100644 index 00000000..e1994326 --- /dev/null +++ b/orchestra/contrib/tasks/README.md @@ -0,0 +1,6 @@ +This is a wrapper around djcelery and celery `@task` and `@periodic_task` decorators. It provides transparent support for switching between executing a task on a plain Python thread or +pushing the task on a queue (rabbitmq) and executing it on a Celery worker. + +A queueless threaded execution has the advantage of 0 moving parts instead of the alternative rabbitmq and celery workers. Less dependencies, less memory footprint, less points of failure. + +If your application needs to run thousands or milions of tasks a day, use celery as your backend, if tens or hundreds, then probably the default thread backend will be your best choice.