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.
Que is a tool in the Background Processing category of a tech stack.
Que is an open source tool with 1.5K GitHub stars and 119 GitHub forks. Here’s a link to Que's open source repository on GitHub
Who uses Que?
3 companies use Que in their tech stacks, including Cerebelo, Connected Bits, and Homer Logistics.
No developer stacks found
Why developers like Que?
Here’s a list of reasons why companies and developers use Que
Be the first to leave a pro
- Transactional Control
- Atomic Backups
- Fewer Dependencies
Que Alternatives & Comparisons
What are some alternatives to Que?
See all alternatives
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.
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.
Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.
Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks.
Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs.