Azure Cosmos DB vs Celery: What are the differences?
Developers describe Azure Cosmos DB as "A fully-managed, globally distributed NoSQL database service". Azure DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development. On the other hand, Celery is detailed 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.
Azure Cosmos DB can be classified as a tool in the "NoSQL Database as a Service" category, while Celery is grouped under "Message Queue".
"Best-of-breed NoSQL features" is the primary reason why developers consider Azure Cosmos DB over the competitors, whereas "Task queue" was stated as the key factor in picking Celery.
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.
Udemy, Sentry, and Postmates are some of the popular companies that use Celery, whereas Azure Cosmos DB is used by Microsoft, Property With Potential, and Rumble. Celery has a broader approval, being mentioned in 272 company stacks & 77 developers stacks; compared to Azure Cosmos DB, which is listed in 24 company stacks and 24 developer stacks.
What is Azure Cosmos DB?
What is Celery?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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.
Using Celery, the web service creates tasks that are executed by a background worker. Celery uses a RabbitMQ instance as a task queue.