Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Sidekiq
Sidekiq

843
402
+ 1
404
Workq
Workq

0
5
+ 1
0
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.

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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Sidekiq?
Why do developers choose Workq?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
        Be the first to leave a con
        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
            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
            Decisions about Sidekiq and Workq
            Jerome Dalbert
            Jerome Dalbert
            Senior Backend Engineer at StackShare | 4 upvotes 34.5K views
            atGratify CommerceGratify Commerce
            delayed_job
            delayed_job
            Rails
            Rails
            AWS Elastic Beanstalk
            AWS Elastic Beanstalk
            Sidekiq
            Sidekiq
            Ruby
            Ruby
            Amazon SQS
            Amazon SQS
            #BackgroundProcessing

            delayed_job is a great Rails background job library for new projects, as it only uses what you already have: a relational database. We happily used it during the company鈥檚 first two years.

            But it started to falter as our web and database transactions significantly grew. Our app interacted with users via SMS texts sent inside background jobs. Because the delayed_job daemon ran every couple seconds, this meant that users often waited several long seconds before getting text replies, which was not acceptable. Moreover, job processing was done inside AWS Elastic Beanstalk web instances, which were already under stress and not meant to handle jobs.

            We needed a fast background job system that could process jobs in near real-time and integrate well with AWS. Sidekiq is a fast and popular Ruby background job library, but it does not leverage the Elastic Beanstalk worker architecture, and you have to maintain a Redis instance.

            We ended up choosing active-elastic-job, which seamlessly integrates with worker instances and Amazon SQS. SQS is a fast queue and you don鈥檛 need to worry about infrastructure or scaling, as AWS handles it for you.

            We noticed significant performance gains immediately after making the switch.

            #BackgroundProcessing

            See more
            Jerome Dalbert
            Jerome Dalbert
            Senior Backend Engineer at StackShare | 3 upvotes 16.9K views
            atStackShareStackShare
            Sidekiq
            Sidekiq
            Ruby
            Ruby
            delayed_job
            delayed_job
            Redis
            Redis

            We use Sidekiq to process millions of Ruby background jobs a day under normal loads. We sometimes process more than that when running one-off backfill tasks.

            With so many jobs, it wouldn't really make sense to use delayed_job, as it would put our main database under unnecessary load, which would make it a bottleneck with most DB queries serving jobs and not end users. I suppose you could create a separate DB just for jobs, but that can be a hassle. Sidekiq uses a separate Redis instance so you don't have this problem. And it is very performant!

            I also like that its free version comes "batteries included" with:

            • A web monitoring UI that provides some nice stats.
            • An API that can come in handy for one-off tasks, like changing the queue of certain already enqueued jobs.

            Sidekiq is a pleasure to use. All our engineers love it!

            See more
            Interest over time
            Reviews of Sidekiq and Workq
            Review ofSidekiqSidekiq

            Pretty good post. I found your website perfect for my needs bullet force

            How developers use Sidekiq and Workq
            Avatar of SmartLogic
            SmartLogic uses SidekiqSidekiq

            We turn to Sidekiq when we need to run background jobs in a Rails app, which we do for just about every Rails app we write. We especially like the ops tools that come with Sidekiq, which make it easy to monitor and maintain.

            Avatar of Tim Lucas
            Tim Lucas uses SidekiqSidekiq

            Background processing of Pushover push notifications to admins when sales occur, payments processing via Pin Payments, Campaign Monitor transaction email sending, and Intercom event API posting.

            Avatar of Told
            Told uses SidekiqSidekiq

            Sidekiq is used extensively for a multitude of background jobs, everything from audio/video post-processing to sending push notifications.

            Avatar of Jeff Flynn
            Jeff Flynn uses SidekiqSidekiq

            We offload our background processing tasks (photo sizing, watermarking, etc.) to Sidekiq to keep our app's performance optimal.

            How much does Sidekiq cost?
            How much does Workq cost?
            Pricing unavailable
            Pricing unavailable
            News about Workq
            More news