What is Workq?
Workq is a job scheduling server strictly focused on simplifying job processing and streamlining coordination. It can run jobs in blocking foreground or non-blocking background mode.
Workq is a tool in the Background Processing category of a tech stack.
Workq is an open source tool with 1.5K GitHub stars and 77 GitHub forks. Here’s a link to Workq's open source repository on GitHub
Who uses Workq?
No company stacks found
No developer stacks found
Why developers like Workq?
Here’s a list of reasons why companies and developers use Workq
Be the first to leave a pro
Workq Alternatives & Comparisons
What are some alternatives to Workq?
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.
No related comparisons found