search

nesquena / backburner

Simple and reliable beanstalkd job queue for ruby
http://nesquena.github.com/backburner
MIT License
429 stars 69 forks source link

Backburner vs beaneater #32

Closed shrekuntu closed 11 years ago

shrekuntu commented 11 years ago

Not really an issue, I just don't know where is the best place to ask this question. I'm just starting with background jobs and wondering what is advantage of backburner over beaneater?

Shreko

nesquena commented 11 years ago

Backburner is built on top of beaneater. It is powered by beaneater but is intended to give you a specific DSL for adding background jobs ala delayed_job or resque. The syntax for adding jobs is easier. Also, backburner has much better worker support to make processing jobs more efficient (theres a forking or threaded worker), more robust retry support and extensible hooks for plugins (i.e https://github.com/nesquena/backburner_mailer).

Rule of thumb: if you are using beanstalkd just for processing jobs similar to delayed_job, use backburner. If you are using beanstalkd for multiple purposes or for anything more complex, then use beaneater. Let me know if you have any more specific questions.