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

Azure Service Bus

188
442
+ 1
7
Celery

1.4K
1.5K
+ 1
279
Add tool

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.

Advice on Azure Service Bus and Celery
André Almeida
Technology Manager at GS1 Portugal - Codipor · | 5 upvotes · 273.6K 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
Matt Madzia
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
  • 98
    Task queue
  • 63
    Python integration
  • 40
    Django integration
  • 30
    Scheduled Task
  • 19
    Publish/subsribe
  • 8
    Various backend broker
  • 6
    Easy to use
  • 5
    Workflow
  • 5
    Great community
  • 4
    Free
  • 1
    Dynamic

Sign up to add or upvote prosMake informed product decisions

Cons of Azure Service Bus
Cons of Celery
  • 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
53
70770
JavaScriptGitHubPython+42
52
20640
GitHubPythonSlack+25
7
2981
GitHubPythonDocker+24
13
16831
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