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.9K GitHub stars and 163 GitHub forks. Here’s a link to Que's open source repository on GitHub
Who uses Que?
5 companies reportedly use Que in their tech stacks, including Transcripto, Homer Logistics, and Connected Bits.
10 developers on StackShare have stated that they use Que.
- 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.
It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
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.
It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc.