Live data from Hacker News

The Many Problems with Celery

steve.dignam.xyz

1–10 of 13 posts

Re: The Many Problems with Celery

#2
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

#3
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

#7
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

#9

I came here to air my grievances with the vegetable. Alas, not tonight.

Have you tried it with peanut butter? It causes all jobs to work swimmingly.

The problem is that it's difficult to add raisins without them being consumed sequentially.

Re: The Many Problems with Celery

#10
post #9

Earlier quoted context omitted.

Have you tried it with peanut butter? It causes all jobs to work swimmingly.

The problem is that it's difficult to add raisins without them being consumed sequentially.

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.
Post reply on HN