I tried to use Celery for something extremely trivial (granted, 5+ years ago). It was so badly documented and failed to do basic things I would expect from a task queue (like progress reporting) I have no idea why it was and still is popular.
I tried to use Celery for something extremely trivial (granted, 5+ years ago). It was so badly documented and failed to do basic things I would expect from a task queue (like progress reporting) I have no idea why it was and still is popular.
Just because you couldn't figure it out doesn't mean the capability wasn't there. More than ten years ago at this point I was running a massively scaled Celery + RabbitMQ + Redis deployment with excellent off-the-shelf reporting using Flower.
I'm going to back GP, eight years ago my team developed a system that was basically an async, scheduled, async task queue, we used celery, and it was so buggy and so troublesome that at some point we switched to a hastily hacked own solution and it worked better.
It's entirely likely that we did something wrong and misused celery. But if many people have problems with using a system correctly then it's also something worth considering.
I hated celery so much I wrote my own message queue.
There’s not much software I really dislike but Celery is one.
A nightmare within a nightmare to configure and run.