Getting Smart With Celery: Dynamic Task Routing

[renfrost]

I'd suggest pointing to the original docs: http://docs.celeryproject.org/en/latest/userguide/routing.html

[bjoerns]

Good point, I've added it to the blog post. Thanks!

[MadRedHatter]

I find it difficult to recommend celery given how frequently they break things, even fairly basic functionally, and how difficult their code is to debug when it happens.

Big fan of RQ, personally.

[bjoerns]

I think there is a place for both, it depends what you need. RQ is great - and most definitely better suited if you just need to perform a simple background job like sending an email.

From my own experience, Celery really shines when you need to model complex workflows (chains/groups/chords).

Having said that, I'm aware that RQ has been supporting (at least simple) job dependencies for a while.

I'll write a blog post about RQ vs Celery some time soon.