Sidekiq vs Workq

Overview

Sidekiq

Stacks1.2K

Followers632

Votes408

Workq

Stacks1

Followers5

Votes0

GitHub Stars1.5K

Forks74

Sidekiq vs Workq: What are the differences?

Sidekiq: Simple, efficient background processing for Ruby. 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; Workq: Job server in Go. 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.

Sidekiq and Workq belong to "Background Processing" category of the tech stack.

Sidekiq and Workq are both open source tools. It seems that Sidekiq with 9.68K GitHub stars and 1.67K forks on GitHub has more adoption than Workq with 1.51K GitHub stars and 77 GitHub forks.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

Detailed Comparison

Sidekiq	Workq
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.	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.
Statistics
GitHub Stars -	GitHub Stars 1.5K
GitHub Forks -	GitHub Forks 74
Stacks 1.2K	Stacks 1
Followers 632	Followers 5
Votes 408	Votes 0
Pros & Cons
Pros 124 Simple 99 Efficient background processing 60 Scalability 37 Better then resque 26 Great documentation	No community feedback yet

What are some alternatives to Sidekiq, Workq?

Beanstalkd

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.

Hangfire

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.

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.

delayed_job

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.

Faktory

Redis -> Sidekiq == Faktory -> Faktory. Faktory is a server daemon which provides a simple API to produce and consume background jobs. Jobs are a small JSON hash with a few mandatory keys.

Kue

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.

Bull

The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.

Cron

Background-only application which launches and runs other applications, or opens documents, at specified dates and times.

PHP-FPM

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.

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.