Faktory vs Que

Overview

Que

Stacks16

Followers20

Votes0

Faktory

Stacks7

Followers27

Votes3

GitHub Stars6.0K

Forks236

Faktory vs Que: What are the differences?

Developers describe Faktory as "Background jobs for any language, by the makers of Sidekiq". 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. 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.

Faktory and Que can be primarily classified as "Background Processing" tools.

Faktory and Que are both open source tools. It seems that Faktory with 3.41K GitHub stars and 136 forks on GitHub has more adoption than Que with 1.47K GitHub stars and 122 GitHub forks.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

Detailed Comparison

Que	Faktory
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.	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.
Concurrency; Efficiency; Safety;Transactional Control;Atomic Backups;Fewer Dependencies; Security	-
Statistics
GitHub Stars -	GitHub Stars 6.0K
GitHub Forks -	GitHub Forks 236
Stacks 16	Stacks 7
Followers 20	Followers 27
Votes 0	Votes 3
Pros & Cons
No community feedback yet	Pros 2 Worker language agnostic 1 Simple service API
Integrations
No integrations available	Node.js Ruby Python Golang Elixir PHP Java JavaScript

What are some alternatives to Que, Faktory?

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.

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.

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.

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.

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.