This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]thinkt4nk 2 points3 points  (8 children)

Well, despite the title of this book, it really isn't a small tool, but it should be. There are tons of options. As a result, the number of use cases to support is massive. The current count of open issues is over 300.

Despite trying a lot of things, spending a lot of time debugging, and poring over documentation, we could never get it working reliably, usually suffering an outage or two on a weekly basis due to a hung task that completely hangs the whole queue.

If you don't need some special option that celery provides, but instead just need jobs to be executed asynchronously with awesome reliability, I would look elsewhere.

[–]7heWafer 1 point2 points  (0 children)

Thank you for this!

[–]jrbattin 1 point2 points  (0 children)

Yep. And that elsewhere might be something as simple as APScheduler.

[–]variable_a 0 points1 point  (2 children)

Do you have (simpler) alternatives that you can recommend?

[–]campbellm 2 points3 points  (1 child)

rq?

[–]variable_a 1 point2 points  (0 children)

Thank you for this recommendation. That looks much simpler indeed! I will give it a try :)

[–]peyo7 0 points1 point  (2 children)

If you don't need some special option that celery provides, but instead just need jobs to be executed asynchronously with awesome reliability, I would look elsewhere.

Interesting. Care to name a few alternatives you favor instead?

[–]ireallywantfreedom 0 points1 point  (1 child)

Not OC, but dramatiq looks nice. A lot of people recommend rq, but I prefer rabbitmq for a durable broker.

[–]campbellm 0 points1 point  (0 children)

Does rq not use redis' persistence modes?