Stacks983

Followers503

+ 1

Votes407

Workq

Stacks0

Followers5

+ 1

Votes0

Add tool

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.

Pros of Sidekiq

Pros of Workq

123
Simple
99
Efficient background processing
60
Scalability
37
Better then resque
26
Great documentation
15
Admin tool
14
Great community
8
Integrates with redis automatically, with zero config
7
Great support
7
Stupidly simple to integrate and run on Rails/Heroku
3
Ruby
3
Freeium
2
Pro version
1
Dashboard w/live polling
1
Great ecosystem of addons
1
Fast

No pros available

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

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 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.

What companies use Sidekiq?

What companies use Workq?

No companies found

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Sidekiq?

What tools integrate with Workq?

No integrations found

Blog Posts

Kafka and Ruby, a Sidekiq Love Story

Jun 6 2019 at 5:11PM

AppSignal

1020

The Stack That Helped Opendoor Buy and Sell Over $1B in Homes

Mar 9 2017 at 8:02AM

Opendoor

+39

30923

How Cotap Is Building A HIPAA-compliant Messaging Service On A...

Jun 26 2015 at 10:14AM

Zinc

+39

1108

How 500px serves up over 500TB of high res photos

May 15 2015 at 3:43PM

500px

+44

109

49612

From Minimum Triable Product to MVP - Building A Status Monito...

May 8 2015 at 4:27PM

StatusGator

+20

735

How Gusto Processes Billions Of Dollars In Annual Payroll

Apr 17 2015 at 2:44AM

Gusto

+29

2432

What are some alternatives to Sidekiq and Workq?

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.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

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.

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

See all alternatives

Interest over time

News about Sidekiq

Cleanly Scaling Sidekiq

(blog.honeybadger.io)

Oct 31, 2017

More news

News about Workq

More news