Celery – Best Practices
In many projects Celery is overkill. Common scenario I saw:<p><pre><code>  1. We have problem, lets use Celery
  2. Now we have one more problem.
</code></pre>
I found <a href="http://python-rq.org/" rel="nofollow">http://python-rq.org/</a> much more handy and cover most cases. It uses redis as query broker. Flask, Django integration included <a href="https://github.com/mattupstate/flask-rq/" rel="nofollow">https://github.com/mattupstate/flask-rq/</a> <a href="https://github.com/ui/django-rq" rel="nofollow">https://github.com/ui/django-rq</a>