Software Alternatives & Reviews

NServiceBus VS Resque

Compare NServiceBus VS Resque and see what are their differences

NServiceBus logo NServiceBus

NServiceBus is a service bus for .NET offering enterprise-grade scalability and reliability for your workflows and integrations.

Resque logo Resque

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

NServiceBus videos

NServiceBus on DNR TV HD

More videos:

  • Review - Udi Dahan presenting on NServiceBus principles (Part 2 of 2)

Resque videos

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

+ Add video

Category Popularity

0-100% (relative to NServiceBus and Resque)
Data Integration
47 47%
53% 53
Web Service Automation
57 57%
43% 43
Stream Processing
22 22%
78% 78
ETL
100 100%
0% 0

User comments

Share your experience with using NServiceBus and Resque. 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 seems to be more popular. 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.

NServiceBus mentions (0)

We have not tracked any mentions of NServiceBus yet. Tracking of NServiceBus recommendations started around Mar 2021.

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

What are some alternatives?

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

Software AG webMethods - Software AG’s webMethods enables you to quickly integrate systems, partners, data, devices and SaaS applications

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

Azure Service Bus - Learn how to set up messaging that connects applications and services across on-premises and cloud environments. Tutorials, videos, API references, and more.

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

IBM App Connect - IBM App Connect is the all-in-one integration tool for connecting apps, integrating data, building APIs and acting on events

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