title: Pros and cons to use Celery vs. RQ
body: <p>Currently I'm working on python project that requires implement some background jobs (mostly for email sending and heavily database updates). I use Redis for task broker. So in this point I have two candidates: <a href="http://celeryproject.org/">Celery</a> and <a href="http://python-rq.org/">RQ</a>. I had some experience with these job queues, but I want to ask you guys to share you experience of using this tools. So.</p>
  
  <ol>
  <li>What pros and cons to use Celery vs. RQ.</li>
  <li>Any examples of projects/task suitable to use Celery vs. RQ.</li>
  </ol>
  
  <p>Celery looks pretty complicated but it's full featured solution. Actually I don't think that I need all these features. From other side RQ is very simple (e.g configuration, integration), but it seems that it lacks some useful features (e.g task revoking, code auto-reloading)</p>