[andrewstuart]

>> So is it Celery then? This awesome library has its fair share of complaints about duplicated task execution — most are due to misconfiguration. I scanned dozens of Stack Overflow threads and GitHub issues in Celery’s repository. Very few were relevant to my case, and none of the fixes were.

I was so annoyed by the pain of configuring Celery I stopped my project and wrote my own job queuing system.

Job and message queues are ridiculously over complicated - including the one I wrote. For trivial usage, job queuing should be zero config.

[andybak]

Hell yeah. And people it them for low-load situations where they could just use a db table or even just spawining a new process. 30k lines of code and several binary dependencies to run a handful of tasks because "it's the best way to do it".

[danjac]

If you just need to send a set of emails once a week, the lowly cron job is fine. You don't need celerybeat.

RQ or Huey are otherwise fine for anything more complicated. I've rarely run into a situation where Celery is better, but teams just use it because it's the "default".

[jwmoz]

+1 Celery is awful. Gave up on it a few years ago Now just use simple asyncio scripts.

[fernandotakai]

i wanna love celery but it's damn bloated that i gave up on using it.

nowadays, if i need to connect to rabbitmq directly, i just use pika/aio-pika, which are lower level, but a LOT more reliable and lightweight.