Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would like to write a Node.js UDP server on Heroku and plan to queue up the data to a Rails instance (dyno) for it to process? What are the pros and cons of using Delayed Job vs RabbitMQ? Thanks, Chirag
These are very hard to compare! RabbitMQ is a messaging system, while delayed_job is a database-backed task queue.
With RabbitMQ you can create a task queue, but that is just one of many use cases.
One could say that delayed_job is a very limited implementation of a task queue,, as the database is not suited for this kind of work.
(see e.g. http://www.rabbitmq.com/resources/RabbitMQ_Oxford_Geek_Night.pdf)
The database may work good enough for simple setups, but it is likely to eventually
fall apart.
If you want a task queue, I suggest you look for one that supports RabbitMQ.