Celery vs Sidekiq: What are the differences?
Developers describe Celery as "Distributed task queue". 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. On the other hand, Sidekiq is detailed as "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.
Celery and Sidekiq are primarily classified as "Message Queue" and "Background Processing" tools respectively.
"Task queue" is the top reason why over 84 developers like Celery, while over 120 developers mention "Simple" as the leading cause for choosing Sidekiq.
Celery and Sidekiq are both open source tools. It seems that Celery with 12.7K GitHub stars and 3.3K forks on GitHub has more adoption than Sidekiq with 9.66K GitHub stars and 1.66K GitHub forks.
StackShare, SendGrid, and New Relic are some of the popular companies that use Sidekiq, whereas Celery is used by Sentry, Ansible, and OpenLabel. Sidekiq has a broader approval, being mentioned in 346 company stacks & 77 developers stacks; compared to Celery, which is listed in 271 company stacks and 77 developer stacks.
What is Celery?
What is Sidekiq?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Sidekiq?
Sign up to get full access to all the companiesMake informed product decisions
All of our background jobs (e.g., image resizing, file uploading, email and SMS sending) are done through Celery (using Redis as its broker). Celery's scheduling and retrying features are especially useful for error-prone tasks, such as email and SMS sending.
For orchestrating the creation of the correct number of instances, managing errors and retries, and finally managing the deallocation of resources we use RabbitMQ in conjunction with the Celery Project framework, along with a self-developed workflow engine.
We maintain a fork of Celery 3 that adds HTTPS support for Redis brokers. The Winning Model currently uses Celery 3 because Celery 4 dropped support for Windows.
We plan on migrating to Celery 4 once Azure ASE supports Linux apps
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.
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.
We used celery, in combination with RabbitMQ and celery-beat, to run periodic tasks, as well as some user-initiated long-running tasks on the server.
Sidekiq is used extensively for a multitude of background jobs, everything from audio/video post-processing to sending push notifications.
Using Celery, the web service creates tasks that are executed by a background worker. Celery uses a RabbitMQ instance as a task queue.