PHP-FPM vs Que

Overview

Que

Stacks16

Followers20

Votes0

PHP-FPM

Stacks121

Followers119

Votes0

PHP-FPM vs Que: What are the differences?

PHP-FPM: * An alternative FastCGI daemon for PHP*. 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: 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.

PHP-FPM and Que can be primarily classified as "Background Processing" tools.

Que is an open source tool with 1.49K GitHub stars and 124 GitHub forks. Here's a link to Que's open source repository on GitHub.

nefisyemektarifleri.com, OTTLabs, and ARENA are some of the popular companies that use PHP-FPM, whereas Que is used by ExperEDU, Cerebelo, and Connected Bits. PHP-FPM has a broader approval, being mentioned in 9 company stacks & 8 developers stacks; compared to Que, which is listed in 4 company stacks and 6 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

Que	PHP-FPM
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.	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.
Concurrency; Efficiency; Safety;Transactional Control;Atomic Backups;Fewer Dependencies; Security	-
Statistics
Stacks 16	Stacks 121
Followers 20	Followers 119
Votes 0	Votes 0

What are some alternatives to Que, PHP-FPM?

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.

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.