delayed_job vs Resque: What are the differences?
delayed_job: Database backed asynchronous priority queue -- Extracted from Shopify. Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks; Resque: A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later. Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.
delayed_job and Resque can be primarily classified as "Background Processing" tools.
"Easy to get started" is the primary reason why developers consider delayed_job over the competitors, whereas "Free" was stated as the key factor in picking Resque.
delayedjob and Resque are both open source tools. It seems that Resque with 8.53K GitHub stars and 1.58K forks on GitHub has more adoption than delayedjob with 4.45K GitHub stars and 915 GitHub forks.
MAK IT, Stitched, and Youboox are some of the popular companies that use Resque, whereas delayedjob is used by Ubiqua, WeLab Limited, and feedforce Inc.. Resque has a broader approval, being mentioned in 34 company stacks & 8 developers stacks; compared to delayedjob, which is listed in 8 company stacks and 5 developer stacks.