Software Alternatives & Reviews
Register | Login

delayed_job VS Resque

Compare delayed_job VS Resque and see what are their differences

Cyclr
Powerful SaaS integration toolkit for SaaS developers - create, amplify, manage and publish native integrations from within your app. featured
Contents:
  1. » Base Details
  2. » Reviews
  3. » Alternatives

delayed_job logo delayed_job

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

Resque logo Resque

Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
  • delayed_job Landing page
    Landing page //
    2022-11-02
  • Resque Landing page
    Landing page //
    2023-10-04

Category Popularity

0-100% (relative to delayed_job and Resque)

delayed_job

Resque

Data Integration
37 37%
Data Integration
63% 63
Stream Processing
38 38%
Stream Processing
62% 62
Ruby On Rails
44 44%
Ruby On Rails
56% 56
Queueing, Messaging And Background Processing
100 100%
Queueing, Messaging And Background Processing
0% 0

User comments

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

Social recommendations and mentions

Resque might be a bit more popular than delayed_job. We know about 5 links to it since March 2021 and only 4 links to delayed_job. 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.

delayed_job mentions (4)

  • 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
  • Delayed Job vs. Sidekiq: Which Is Better?
    Several gems support job queues and background processing in the Rails world — Delayed Job and Sidekiq being the two most popular ones. - Source: dev.to / about 2 years ago
  • Why does rails have a tradition of queuing background jobs in a separate NoSQL store, when both the queueing controller and the job class tend to hammer the main database anyway?
    Back in the day, before Sidekiq and such, we used Delayed Job https://github.com/collectiveidea/delayed_job. Source: over 2 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

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 / almost 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

What are some alternatives?

When comparing delayed_job and Resque, 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.

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.

RabbitMQ - RabbitMQ is an open source message broker software.

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

Bull - Bull is a Node library that implements a fast and robust queue system based on redis.

Loading...