Celery vs CloudAMQP: 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, CloudAMQP is detailed as "RabbitMQ as a Service". Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms.
Celery and CloudAMQP can be primarily classified as "Message Queue" tools.
"Task queue" is the primary reason why developers consider Celery over the competitors, whereas "Some of the best customer support you'll ever find" was stated as the key factor in picking CloudAMQP.
Celery is an open source tool with 12.9K GitHub stars and 3.33K GitHub forks. Here's a link to Celery's open source repository on GitHub.
According to the StackShare community, Celery has a broader approval, being mentioned in 272 company stacks & 77 developers stacks; compared to CloudAMQP, which is listed in 12 company stacks and 5 developer stacks.
What is Celery?
What is CloudAMQP?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using CloudAMQP?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake 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.