Need advice about which tool to choose?Ask the StackShare community!

Azure Service Bus

549
525
+ 1
7
Celery

1.7K
1.6K
+ 1
280
Add tool

Azure Service Bus vs Celery: What are the differences?

Key Differences between Azure Service Bus and Celery

Azure Service Bus and Celery are both popular messaging frameworks used for handling asynchronous and distributed tasks. Despite their similarities, there are several key differences between the two:

  1. Architecture and Dependency: Azure Service Bus is a cloud-based messaging service provided by Microsoft Azure, while Celery is an open-source distributed task queue system. Azure Service Bus requires an Azure subscription and is directly integrated with other Azure services, while Celery can be used in any environment and with different message brokers.

  2. Language Support: Azure Service Bus supports various programming languages, including .NET, Java, Python, and Node.js. On the other hand, Celery is primarily used with Python and has extensive support for Python-related tools and frameworks.

  3. Scalability and Performance: Azure Service Bus is highly scalable and can handle a large number of messages at a high throughput. It provides advanced features like message batching, session handling, and dead-lettering. Celery, on the other hand, provides scalability to some extent by using distributed message brokers like RabbitMQ or Redis, but it may not be as scalable as Azure Service Bus in certain scenarios.

  4. Service Offering: Azure Service Bus is a fully managed service provided by Microsoft Azure, which means that the infrastructure and maintenance aspects are taken care of by Azure. Celery, being an open-source framework, requires more configuration and setup effort as it needs to be deployed and maintained by the users themselves.

  5. Monitoring and Management: Azure Service Bus provides extensive monitoring and management capabilities through Azure Portal, such as graphical representations of message rates, queues, and subscriptions. It also integrates with Azure Monitor for alerts and diagnostics. Celery, on the other hand, provides basic monitoring capabilities and logging but may require additional tools or customization for comprehensive monitoring and management.

  6. Cost: Azure Service Bus is a paid service, and the cost is based on message volume, throughput, and other factors. The pricing can vary based on the specific Azure region and the chosen pricing tier. Celery, being open-source, is free to use, but users need to consider the infrastructure and resources required to deploy and maintain their own Celery workers and message brokers.

In summary, Azure Service Bus is a cloud-based, fully managed messaging service provided by Microsoft Azure, offering extensive scalability, advanced features, and integration with other Azure services. Celery, on the other hand, is an open-source task queue system primarily used with Python, providing flexibility and customization options for distributed task processing.

Advice on Azure Service Bus and Celery
André Almeida
Technology Manager at GS1 Portugal - Codipor · | 5 upvotes · 406.7K views
Needs advice
on
Azure Service BusAzure Service Bus
and
RabbitMQRabbitMQ

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

See more
Replies (2)

A Pro of Azure Service Bus is reliability and persistence: you can send message when receiver is offline; receiver can read it when it back online. A Cons is costs and message size. You can consider also SignalR

See more
Recommends

There are many different messaging frameworks available for IPC use. It's not really a question of how "new" the technology is, but what you need it to do. Azure Service Bus can be a great service to use, but it can also take a lot of effort to administrate and maintain that can make it costly to use unless you need the more advanced features it offers for routing, sequencing, delivery, etc. I would recommend checking out this link to get a basic idea of different messaging architectures. These only cover Azure services, but there are many other solutions that use similar architectural models.

https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Azure Service Bus
Pros of Celery
  • 4
    Easy Integration with .Net
  • 2
    Cloud Native
  • 1
    Use while high messaging need
  • 99
    Task queue
  • 63
    Python integration
  • 40
    Django integration
  • 30
    Scheduled Task
  • 19
    Publish/subsribe
  • 8
    Various backend broker
  • 6
    Easy to use
  • 5
    Great community
  • 5
    Workflow
  • 4
    Free
  • 1
    Dynamic

Sign up to add or upvote prosMake informed product decisions

Cons of Azure Service Bus
Cons of Celery
  • 1
    Limited features in Basic tier
  • 1
    Skills can only be used in Azure - vendor lock-in
  • 1
    Lacking in JMS support
  • 1
    Observability of messages in the queue is lacking
  • 4
    Sometimes loses tasks
  • 1
    Depends on broker

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Azure Service Bus?

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.

What is Celery?

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Azure Service Bus?
What companies use Celery?
See which teams inside your own company are using Azure Service Bus or Celery.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Azure Service Bus?
What tools integrate with Celery?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

GitHubPythonNode.js+47
54
72283
JavaScriptGitHubPython+42
53
21803
GitHubPythonSlack+25
7
3148
GitHubPythonDocker+24
13
17002
What are some alternatives to Azure Service Bus and Celery?
NServiceBus
Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.
RabbitMQ
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Kafka
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
MSMQ
This technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues.
IBM MQ
It is a messaging middleware that simplifies and accelerates the integration of diverse applications and business data across multiple platforms. It offers proven, enterprise-grade messaging capabilities that skillfully and safely move information.
See all alternatives