News for hackers. Stuff that matters.
Re:The Many Problems with Celery by Something1234 on Sunday May 21, 2023 @09:13PM (#36026296)
Celery has so many issues and this outlines just a few of them. I was working on celery for a while on one of my personal projects and it's just absolutely insane what you have to do to get it working with django. It's so incredibly over engineered nad powered by magic.
Re:The Many Problems with Celery by dikei on Sunday May 21, 2023 @09:57PM (#36026555)
I think Celery is doing itself a disservice by supporting so many brokers and result stores with different behaviors about delivery guarantee, leading to leaky abstraction everywhere.
Re:The Many Problems with Celery by iancmceachern on Sunday May 21, 2023 @10:14PM (#36026681)
I came here to air my grievances with the vegetable. Alas, not tonight.
Re:The Many Problems with Celery by 1letterunixname on Monday May 22, 2023 @12:30PM (#36033538)
Have you tried it with peanut butter? It causes all jobs to work swimmingly.
Re:The Many Problems with Celery by shaftway on Monday May 22, 2023 @04:49PM (#36036533)
The problem is that it's difficult to add raisins without them being consumed sequentially.
Re:The Many Problems with Celery by iancmceachern on Monday May 22, 2023 @11:26PM (#36039438)
The problem in my view is those tooth floss like strings. They're worse with peanut butter. If one could figure out celery without those terrible strings I'd happily reconsider my opinion on celery.
Re:The Many Problems with Celery by 1letterunixname on Wednesday May 24, 2023 @11:02AM (#36059096)
Very thin slices.
Re:The Many Problems with Celery by z3ugma on Monday May 22, 2023 @08:42AM (#36030677)
For folks who have tried celery, and were dissatisfied with that, what did you switch to? What else is there for python task queues?
Re:The Many Problems with Celery by 1letterunixname on Monday May 22, 2023 @12:40PM (#36033651)
There should be a distinction between a work queue and a job scheduler. The work queue dispatches jobs but doesn't know enough to retry them while the scheduler decides what to retry.

In Rails land, I would opt for Backburner over the commercial choices because it uses beanstalkd. For anything requiring HA, I would look at some sort of queue using an ESB as a transport. Short of HA, shard for LB.

Re:The Many Problems with Celery by Beestie on Monday May 22, 2023 @12:42PM (#36033672)
Celery? Not knowing this was a post about software, I figured it was about the vegatable.

Can't wait until software naming reaches the same absurdity level as racehorse names.

/rant

Re:The Many Problems with Celery by Clamchop on Tuesday May 23, 2023 @01:28AM (#36040229)
I'm personally a fan of Pickle and Cucumber, completely unrelated naturally.
Re:The Many Problems with Celery by fikka0 on Tuesday May 23, 2023 @11:20AM (#36045584)
Steve, this is such a great piece of knowledge! I see you mention lack of monitoring solutions, I'm creating a Celery monitoring tool at the moment, it's already a working/useful MVP, I'd love to get your opinion on it, is there any way to connect?