Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

delayed_job
delayed_job

38
34
+ 1
6
Que
Que

10
8
+ 1
0
Add tool

delayed_job vs Que: What are the differences?

Developers describe delayed_job as "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. On the other hand, Que is detailed as "A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability". Que is a high-performance alternative to DelayedJob or QueueClassic that improves the reliability of your application by protecting your jobs with the same ACID guarantees as the rest of your data.

delayed_job and Que belong to "Background Processing" category of the tech stack.

delayedjob and Que are both open source tools. It seems that delayedjob with 4.46K GitHub stars and 915 forks on GitHub has more adoption than Que with 1.47K GitHub stars and 122 GitHub forks.

What is delayed_job?

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.

What is Que?

Que is a high-performance alternative to DelayedJob or QueueClassic that improves the reliability of your application by protecting your jobs with the same ACID guarantees as the rest of your data.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose delayed_job?
Why do developers choose Que?
    Be the first to leave a pro
    What are the cons of using delayed_job?
    What are the cons of using Que?
      Be the first to leave a con
        Be the first to leave a con
        What companies use delayed_job?
        What companies use Que?

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with delayed_job?
        What tools integrate with Que?
          No integrations found
          What are some alternatives to delayed_job and Que?
          Sidekiq
          Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.
          Resque
          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.
          Beanstalkd
          Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.
          Kue
          Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs.
          Hangfire
          It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
          See all alternatives
          Decisions about delayed_job and Que
          No stack decisions found
          Interest over time
          Reviews of delayed_job and Que
          No reviews found
          How developers use delayed_job and Que
          No items found
          How much does delayed_job cost?
          How much does Que cost?
          Pricing unavailable
          Pricing unavailable
          News about delayed_job
          More news
          News about Que
          More news