Sidekiq vs. Que



  • -
  • -
  • 1.84K
  • -
  • 158
  • 0

What is Sidekiq?

Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.

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!

Why do developers choose Sidekiq?
Why do you like Sidekiq?

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

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

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

How much does Sidekiq cost?
How much does Que cost?
What companies use Sidekiq?
412 companies on StackShare use Sidekiq
What companies use Que?
4 companies on StackShare use Que
What tools integrate with Sidekiq?
2 tools on StackShare integrate with Sidekiq
What tools integrate with Que?
1 tools on StackShare integrate with Que

What are some alternatives to Sidekiq and Que?

  • Resque - A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later
  • 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 Sidekiq

Cleanly Scaling Sidekiq


Interest Over Time