Resque vs. Que

Get help choosing one of these Get news updates about these tools


Favorites

4

Favorites

0

Hacker News, Reddit, Stack Overflow Stats

  • 16
  • 2.04K
  • 1.03K
  • -
  • 115
  • 0

GitHub Stats

Description

What is Resque?

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.

What is 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.

Want advice about which of these to choose?Ask the StackShare community!

Ask a Question

Pros

Why do developers choose Resque?
Why do you like Resque?

Why do developers choose Que?
Why do you like Que?

Cons

What are the cons of using Resque?
No Cons submitted yet for Resque
Downsides of Resque?

What are the cons of using Que?
No Cons submitted yet for Que
Downsides of Que?

Pricing

How much does Resque cost?
How much does Que cost?

Companies

What companies use Resque?
34 companies on StackShare use Resque
What companies use Que?
3 companies on StackShare use Que

Integrations

What tools integrate with Resque?
1 tools on StackShare integrate with Resque
What tools integrate with Que?
1 tools on StackShare integrate with Que

What are some alternatives to Resque and Que?

  • Sidekiq - Simple, efficient background processing for Ruby
  • Beanstalkd - A simple, fast work queue
  • delayed_job - Database backed asynchronous priority queue -- Extracted from Shopify
  • Kue - Kue is a priority job queue backed by redis, built for node.js

See all alternatives to Resque



Interest Over Time


Get help choosing one of these