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. Bull vs Resque

Bull vs Resque

OverviewComparisonAlternatives

Overview

Resque
Resque
Stacks118
Followers126
Votes9
GitHub Stars9.5K
Forks1.7K
Bull
Bull
Stacks92
Followers113
Votes1
GitHub Stars16.2K
Forks1.4K

Bull vs Resque: What are the differences?

  1. Storage: Bull uses Redis for storage, while Resque stores data in Redis as well but also relies on additional dependencies like Ruby and Rake.
  2. Initiative Development: Bull is developed and maintained by Node.js developers, ensuring a more Node.js-centric approach, whereas Resque is primarily developed and maintained by Ruby developers with a focus on the Ruby ecosystem.
  3. Concurrency Handling: Bull allows for multiple concurrent processes for jobs, enabling greater efficiency in processing, whereas Resque processes jobs sequentially, potentially leading to slower execution.
  4. Retry Strategies: Bull has built-in support for retrying failed jobs with customizable strategies, providing more flexibility and control, while Resque lacks this feature and may require manual intervention for retrying failed jobs.
  5. Job Prioritization: Bull supports job prioritization, allowing for the assignment of different priorities to jobs for efficient task handling, whereas Resque does not have built-in support for job prioritization.
  6. Event Handling: Bull provides robust event handling mechanisms, enabling developers to easily listen for various events in the job lifecycle, while Resque lacks comprehensive event handling capabilities.

In Summary, Bull and Resque differ in storage, development focus, concurrency handling, retry strategies, job prioritization, and event handling capabilities.

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

Resque
Resque
Bull
Bull

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.

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

-
Minimal CPU usage due to a polling-free design.; Robust design based on Redis.; Delayed jobs.; Schedule and repeat jobs according to a cron specification.; Rate limiter for jobs.; Retries.; Priority.; Concurrency.; Pause/resume—globally or locally.; Multiple job types per queue.; Threaded (sandboxed) processing functions.; Automatic recovery from process crashes.
Statistics
GitHub Stars
9.5K
GitHub Stars
16.2K
GitHub Forks
1.7K
GitHub Forks
1.4K
Stacks
118
Stacks
92
Followers
126
Followers
113
Votes
9
Votes
1
Pros & Cons
Pros
  • 5
    Free
  • 3
    Scalable
  • 1
    Easy to use on heroku
Pros
  • 1
    Ease of use
Integrations
No integrations available
Node.js
Node.js

What are some alternatives to Resque, Bull?

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.

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.

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.

Que

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.

Goose

Goose

It is a simple, reliable & scalable background processing library for Clojure. It has a transparent design & cloud-native architecture.

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