News for hackers. Stuff that matters.

Python/Django devs: do you use Celery? And why does it suck for you?

I have joined a new company lately and they heavily use Celery for background tasks (mails, analytics, etc.) for their Django app.

I haven't used it before but I now noticed it sucks. I genuinely don't understand what it offers to developers above standalone RabbitMQ + cron jobs.

And it adds more complexity and reduces transparency a lot.

I was wondering if others share my point of view or do you think Celery is awesome?

( 1 comment | 3 points | on HN )
Re:Python/Django devs: do you use Celery? And why does it su... by BiteCode_dev on Tuesday June 11, 2024 @05:55AM (#40644396)
Not anymore because it's been a burden.

But it doesn't bring more than rabbit MQ:

- it stores results

- it stores exceptions

- it gives them back to you in native form

- it has a UI admin for tasks

- it can use multiple backends, including redis and a db

Now I tend to use simpler things when the project allows it, like huey and rq. Most of the time, you don't need something super powerful for your tasks.