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

Resque Alternatives

Similar projects and alternatives to Resque

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Resque alternative or higher similarity.

Resque reviews and mentions

Posts with mentions or reviews of Resque. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-14.
  • Mike Perham of Sidekiq: “If you build something valuable, charge money for it.”
    6 projects | | 14 Apr 2023
    The free version acts exactly like Resque, the previous market leader in Ruby background jobs. If it was good enough reliability for GitHub and Shopify to use for years, it was good enough for Sidekiq OSS too.

    Here's Resque literally using `lpop` which is destructive and will lose jobs.

  • Add web scraping data into the database at regular intervals [ruby & ror]
    2 projects | /r/learnprogramming | 16 Jun 2022
    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.
  • How to run a really long task from a Rails web request
    3 projects | | 18 Apr 2022
    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 block other important background tasks for so long.
  • Building a dynamic staging platform
    5 projects | | 14 Apr 2022
    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.
  • Autoscaling Redis applications on Kubernetes 🚀🚀
    9 projects | | 2 Mar 2021
    Redis Lists are quite versatile and used as the backbone for implementing scalable architectural patterns such as consumer-producer (based on queues), where producer applications push items into a List, and consumers (also called workers) process those items. Popular projects such as resque, sidekiq, celery etc. use Redis behind the scenes to implement background jobs.
  • A note from our sponsor - PopRuby | 1 Mar 2024
    Fashion meets Ruby! Shop our fun Ruby-inspired apparel and accessories designed to celebrate the joy and diversity of the Ruby community. Learn more →


Basic Resque repo stats
3 months ago
The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.