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

delayed_job

47
55
+ 1
6
Hangfire

113
151
+ 1
16
Add tool

delayed_job vs Hangfire: 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, Hangfire is detailed as "Perform background processing in .NET and .NET Core applications". 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.

delayed_job and Hangfire can be categorized as "Background Processing" tools.

delayedjob and Hangfire are both open source tools. Hangfire with 4.93K GitHub stars and 1.12K forks on GitHub appears to be more popular than delayedjob with 4.47K GitHub stars and 915 GitHub forks.

According to the StackShare community, delayed_job has a broader approval, being mentioned in 13 company stacks & 23 developers stacks; compared to Hangfire, which is listed in 9 company stacks and 9 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of delayed_job
Pros of Hangfire
  • 3
    Easy to get started
  • 2
    Reliable
  • 1
    Doesn't require Redis
  • 6
    Integrated UI dashboard
  • 5
    Simple
  • 3
    Robust
  • 2
    In Memory
  • 0
    Cons
  • 0
    Simole

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

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 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.

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

What companies use delayed_job?
What companies use Hangfire?
See which teams inside your own company are using delayed_job or Hangfire.
Sign up for Private StackShareLearn More

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

What tools integrate with delayed_job?
What tools integrate with Hangfire?
    No integrations found
    What are some alternatives to delayed_job and Hangfire?
    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.
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    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.
    PHP-FPM
    It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc.
    See all alternatives