Hangfire vs delayed_job

Overview

delayed_job

Stacks53

Followers65

Votes6

GitHub Stars4.8K

Forks952

Hangfire

Stacks333

Followers249

Votes17

GitHub Stars9.9K

Forks1.7K

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.

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

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

delayed_job	Hangfire
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.	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.
Statistics
GitHub Stars 4.8K	GitHub Stars 9.9K
GitHub Forks 952	GitHub Forks 1.7K
Stacks 53	Stacks 333
Followers 65	Followers 249
Votes 6	Votes 17
Pros & Cons
Pros 3 Easy to get started 2 Reliable 1 Doesn't require Redis	Pros 7 Integrated UI dashboard 5 Simple 3 Robust 2 In Memory 0 Simole

What are some alternatives to delayed_job, 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.

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.

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.

Faktory

Redis -> Sidekiq == Faktory -> Faktory. Faktory is a server daemon which provides a simple API to produce and consume background jobs. Jobs are a small JSON hash with a few mandatory keys.

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.

Bull

The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.

Cron

Background-only application which launches and runs other applications, or opens documents, at specified dates and times.

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.

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.