Azure Service Bus vs Celery: What are the differences?
Azure Service Bus: Reliable cloud messaging as a service (MaaS) *. It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline; *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.
Azure Service Bus and Celery can be categorized as "Message Queue" tools.
Celery is an open source tool with 13.1K GitHub stars and 3.36K 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 355 company stacks & 455 developers stacks; compared to Azure Service Bus, which is listed in 11 company stacks and 8 developer stacks.
What is Azure Service Bus?
What is Celery?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Azure Service Bus?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Azure Service Bus?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Azure Service Bus?
As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.
Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.
Automations are what makes a CRM powerful. With Celery and RabbitMQ we've been able to make powerful automations that truly works for our clients. Such as for example, automatic daily reports, reminders for their activities, important notifications regarding their client activities and actions on the website and more.
We use Celery basically for everything that needs to be scheduled for the future, and using RabbitMQ as our Queue-broker is amazing since it fully integrates with Django and Celery storing on our database results of the tasks done so we can see if anything fails immediately.
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.