Menu
I'm wondering what criteria would need to be considered when we need to use some kind of task queue in a django project, I'm thinking in performace, development speed, flexibility, etc.
I've been using Celery+RabbitMQ and Django-ztask+ZeroMQ indistinctly for a while (I'm sure there are another good ones), but I haven't an accurate canon for picking up the most suitable in each case.
Could you provide some peculiarities for each of them that allows the user chooses between them?, does it might include some another stable MQ approaches as well?
355
Celery makes it easier to implement the task queues for many workers in a Django application.
Yes you can. Celery is a generic asynchronous task queue.
Celery is a task queue implementation for Python web applications used to asynchronously execute work outside the HTTP request-response cycle. Celery is an implementation of the task queue concept.
In Django Background Task, all tasks are implemented as functions (or any other callable). There are two parts to using background tasks: creating the task functions and registering them with the scheduler. setup a cron task (or long running process) to execute the tasks.
I can't provide much but I have used two different solutions, Celery+Redis and Celery+RabbitMQ.
I tried RabbitMQ first and after getting all its dependencies installed and spending some time wading through configs I got it working. It worked well, didn't drop anything, but I was always nervous about restarting (either it or the server) because I was never completely sure it would come back up. I'm sure that's my fault, but I couldn't work out what I'd done wrong.
So I thought I'd give Redis a try. Installed and configured it in about 3 minutes and it has worked without any of my attention since.
Now if only there was something easier to configure than Celery...
153
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
