Hacker News Reader

Which alternatives worked for you?

Can't speak for op, but for us the ones based on RabbitMQ have performed well:

Stay away from Celery if you can, or stick to v3.2 because 4.x has a ton of bugs.

Celery has always been a massive resource drain, and for pretty much zero gain. I'd suggest just saying "stay away from Celery" as it's easy to get going with, but really hard to scale or work with when you need what it promises. There are better options.

Agree that you should stay away from Celery in most cases, but it does integrate well with Django, and pre-4.x is stable enough.

It's just a fairly higher amount of boilerplate and setup compared to most of the alternatives either way.

So far I've mostly used Celery in Python, but at jobs past there was also Sidekiq (granted, the use cases for that were a bit different, but it's kind of in the same bucket).

Haven't had the opportunity to work with them, but I've heard good things about SQS and other cloud queues, but I think those are fundamentally message queues, so you'd be responsible for writing a job queue layer over it, which can be a huge hassle.

Reply on news.ycombinator.com