Celery vs DoctorKafka: 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, DoctorKafka is detailed as "A service for Kafka cluster auto healing and workload balancing". DoctorKafka can automatically detect broker failure and reassign the workload on the failed nodes to other nodes. DoctorKafka can also perform load balancing based on topic partitions's network usage, and makes sure that broker network usage does not exceed the defined settings.
Celery and DoctorKafka can be categorized as "Message Queue" tools.
Celery and DoctorKafka are both open source tools. It seems that Celery with 12.9K GitHub stars and 3.33K forks on GitHub has more adoption than DoctorKafka with 488 GitHub stars and 68 GitHub forks.
What is Celery?
What is DoctorKafka?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose DoctorKafka?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using DoctorKafka?
What companies use DoctorKafka?
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 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.