I've found a few problems with celery myself. It has an absolutely amazing feature set and seems like a clever and very clean abstraction. However, when it st

I've found a few problems with celery myself. It has an absolutely amazing feature set and seems like a clever and very clean abstraction. However, when it starts hiding exceptions within your tasks if you use JSON for messages or if you are having problems with it doing things you were not expecting... Like randomly not passing information between dependant tasks... Gevent and celery I have found don't play well together even if you disable Gevent for the worker. Maybe you eventually realise that writing your own task for rabbitmq and your own workers is simpler than relying on someone elses complex code. Celery will 100% do what you want but it's definitely been a steeper learning curve than it should be and has lots of gotchas and many hours of hunting around to deal with obscure issues. I do wonder if there is a reasonable heuristic, apart from experience, to learn when a piece of software may be too complex for at least me to use well.