By DelayedJob do you mean DelayedJob backed by ActiveRecord/DB? I assume so from how the question is worded.
I'm a big fan of DB backed queues for most situations, especially to start out. One big benefit is you don't need additional infrastructure, assuming you are already using a DB.
DB backed queues can definitely have scaling issues, but depending on the size of your queue and the size of your DB you can put off that issue for almost ever. For example at my job we average over 4 million jobs a day via our DB backed queue.
In general I think DB backed queues are my default, unless the specifics of the project call for something else!
By DelayedJob do you mean DelayedJob backed by ActiveRecord/DB? I assume so from how the question is worded.
I'm a big fan of DB backed queues for most situations, especially to start out. One big benefit is you don't need additional infrastructure, assuming you are already using a DB.
DB backed queues can definitely have scaling issues, but depending on the size of your queue and the size of your DB you can put off that issue for almost ever. For example at my job we average over 4 million jobs a day via our DB backed queue.
In general I think DB backed queues are my default, unless the specifics of the project call for something else!
Thanks for your insights Corey. That's correct, delayed_job in using ActiveRecord and DB based.