Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yep. Celery + RabbitMQ is a pain in the ass for very simple cases. RabbitMQ is more sophisticated than most basic projects require.


I have yet to encounter a legit use case for RabbitMQ.

I'm sure they exist in theory, but it's overkill in every situation that I've seen it deployed.


well, depends on your load! at work, we have millions of message per minute (our whole infrastructure is based on rabbitmq). rabbitmq can handle that load without any issues.

also, rabbitmq has an amazing admin interface, monitoring is really easy (most things you use for monitoring support it) and the whole thing has really sane defaults (imho).

all in all, it's one of my favorites pieces of software ever!


honestly, i always found quite easy to setup. do you remember your issue?

(btw, i remember people having problems with celery because of they way they imported the tasks. if you always do full imports (as in, from a.b.c import tasks instead of from . import tasks) you shouldn't have any issues).


Celery + Redis is way simpler.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: