Hacker News Reader

Comment by brianwawok | Hacker News Reader

The biggest overhead is really setting up RabbitMQ right? Because Django and Celery play nice, you can just deploy one codebase and run 1 Django process and 1 Celery + Celery Beat process pretty easy...

Bummer you lose so many Celery features when you use Amazon or Google Cloud Queues instead of RabbitMQ....

View on HN

Not just setting up, but celery has a learning curve which may or may not be worth your time. Also you have an additional points of complexity (rabbitmq and celery workers) that also have an additional operations maintenance burden. For a small app that doesn't have to scale, I'd avoid it. But when building a business focused web app, I use it a lot, especially for large file parsing.

AFAIK you can have RabitMQ SaaS these days.

And yes, RabbitMQ is very good.

Yes CloudAMQP is such a service. It includes a free plan. If you are going to use Celery and CloudAMQP, I'd advice using the recommended settings[1], otherwise Celery will produce a large number of connections + messages.

(Disclaimer: I work with CloudAMQP)

[1] https://www.cloudamqp.com/docs/celery.html

cloudamqp? I guess, not terribly cheap though.

I think there are a few other options. But deploying RabbitMQ isn't that hard. I can actually write something about that.

Is Linode cheap enough for you?

I mean last time I needed RabbitMQ I just used

https://github.com/Mayeu/ansible-playbook-rabbitmq

and it took 3 minutes. But I hear a lot of people saying not to use Celery because RabbitMQ is hard.. maybe people just have different standards for hard?

Reply on news.ycombinator.com