StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Background Processing
  5. Que vs Subserver

Que vs Subserver

OverviewComparisonAlternatives

Overview

Que
Que
Stacks16
Followers20
Votes0
Subserver
Subserver
Stacks1
Followers0
Votes0
GitHub Stars9
Forks4

Subserver vs Que: What are the differences?

Subserver: A simple server process for processing Google Pubsub messages. It is a background server process for processing messages from Google Pub/Sub It was designed to be an efficient, configurable process that easily integrates into any ruby app.; 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.

Subserver and Que can be categorized as "Background Processing" tools.

Some of the features offered by Subserver are:

  • Threaded multi-subscription support
  • Message processing middleware
  • Auto subscriber loading

On the other hand, Que provides the following key features:

  • Concurrency
  • Efficiency
  • Safety

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

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)
or
Manual

Detailed Comparison

Que
Que
Subserver
Subserver

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 a background server process for processing messages from Google Pub/Sub. It was designed to be an efficient, configurable process that easily integrates into any ruby app.

Concurrency; Efficiency; Safety;Transactional Control;Atomic Backups;Fewer Dependencies; Security
Threaded multi-subscription support; Message processing middleware; Auto subscriber loading; Per subscriber configuration; Error handling and logging
Statistics
GitHub Stars
-
GitHub Stars
9
GitHub Forks
-
GitHub Forks
4
Stacks
16
Stacks
1
Followers
20
Followers
0
Votes
0
Votes
0
Integrations
No integrations available
Google Cloud Pub/Sub
Google Cloud Pub/Sub

What are some alternatives to Que, Subserver?

Sidekiq

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

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

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

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

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

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

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

Bull

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

Cron

Cron

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

PHP-FPM

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.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase