Software Alternatives & Reviews

Resque VS Bull

Compare Resque VS Bull and see what are their differences

Resque logo Resque

Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.

Bull logo Bull

Bull is a Node library that implements a fast and robust queue system based on redis.
  • Resque Landing page
    Landing page //
    2023-10-04
  • Bull Landing page
    Landing page //
    2022-11-02

Resque videos

No Resque videos yet. You could help us improve this page by suggesting one.

+ Add video

Bull videos

Designated Survivor​ Review​, Bull Review - Keifer Sutherland, Michael Weatherly

More videos:

  • Review - Bull power585 tractor price and owner review
  • Review - Energy Crisis--Energy Drink Review #150 Red Bull Summer Edition

Category Popularity

0-100% (relative to Resque and Bull)
Data Integration
64 64%
36% 36
Stream Processing
66 66%
34% 34
Web Service Automation
54 54%
46% 46
Ruby On Rails
81 81%
19% 19

User comments

Share your experience with using Resque and Bull. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, Resque should be more popular than Bull. It has been mentiond 5 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Resque mentions (5)

  • Add web scraping data into the database at regular intervals [ruby & ror]
    You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically. Source: almost 2 years ago
  • How to run a really long task from a Rails web request
    So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago
  • Building a dynamic staging platform
    Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck. - Source: dev.to / about 2 years ago
  • #30DaysofAppwrite : Appwrite’s building blocks
    The Schedules worker corresponds to the appwrite-schedule service in the docker-compose file. The Schedules worker uses a Resque Scheduler under the hood and handles the scheduling of CRON jobs across Appwrite. This includes CRON jobs from the Tasks API, Webhooks API, and the functions API. - Source: dev.to / about 3 years ago
  • A quick look at background jobs in Ruby
    There are a few of popular systems. A few need a database, such as Delayed::Job, while others prefer Redis, such as Resque and Sidekiq. - Source: dev.to / about 3 years ago

Bull mentions (1)

  • Crone Job with dynamic interval
    Use bull queue with “delay” parameter. You can create as many jobs scheduled that way as you want. https://optimalbits.github.io/bull/. Source: about 1 year ago

What are some alternatives?

When comparing Resque and Bull, you can also consider the following products

Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby

Hangfire - An easy way to perform background processing in .NET and .NET Core applications.

delayed_job - Database based asynchronous priority queue system -- Extracted from Shopify - collectiveidea/delayed_job

RabbitMQ - RabbitMQ is an open source message broker software.

Enqueue It - Easy and scalable solution for manage and execute background tasks seamlessly in .NET applications. It allows you to schedule, queue, and process your jobs and microservices efficiently.

Apache Kafka - Apache Kafka is an open-source message broker project developed by the Apache Software Foundation written in Scala.