Celery vs Disque: What are the differences?
What is Celery? 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.
What is Disque? In-memory, distributed job queue. Disque is an ongoing experiment to build a distributed, in-memory, message broker. Its goal is to capture the essence of the "Redis as a jobs queue" use case, which is usually implemented using blocking list operations, and move it into an ad-hoc, self-contained, scalable, and fault tolerant design, with simple to understand properties and guarantees, but still resembling Redis in terms of simplicity, performance, and implementation as a C non-blocking networked server.
Celery and Disque can be primarily classified as "Message Queue" tools.
Celery and Disque are both open source tools. It seems that Celery with 12.9K GitHub stars and 3.33K forks on GitHub has more adoption than Disque with 7.37K GitHub stars and 516 GitHub forks.
What is Celery?
What is Disque?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Disque?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Disque?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Disque?
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 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.