2
I think Celery is a good approach. Not sure if you need Redis/RabbitMQ as a broker or you could just use MySQL – it depends on your tasks. Celery workers could be runned on the different servers, so Celery supports distributed queues.
Another approach – implement some queue engine with python, database as a broker and a cron for job executions. But it could be a dirty way with a lots of pain and bugs.
So I think that Celery is a more nice way to do it.
0
If you are running on Heroku, you want django-rq, not Celery. See https://devcenter.heroku.com/articles/python-rq.
Source:stackexchange.com