Need advice about which tool to choose?Ask the StackShare community!
Azure Service Bus vs NServiceBus: What are the differences?
Developers describe Azure Service Bus as "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. On the other hand, *NServiceBus** is detailed as "*Enterprise-grade scalability and reliability for your workflows and integrations *". Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.
Azure Service Bus and NServiceBus can be primarily classified as "Message Queue" tools.
According to the StackShare community, Azure Service Bus has a broader approval, being mentioned in 11 company stacks & 8 developers stacks; compared to NServiceBus, which is listed in 9 company stacks and 6 developer stacks.
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 :)
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
Pros of Azure Service Bus
- Easy Integration with .Net4
- Cloud Native2
- Use while high messaging need1
Pros of NServiceBus
- Brings on-prem issues to the cloud1
- Not as good as alternatives, good job security1
Sign up to add or upvote prosMake informed product decisions
Cons of Azure Service Bus
- Limited features in Basic tier1
- Skills can only be used in Azure - vendor lock-in1
- Lacking in JMS support1
- Observability of messages in the queue is lacking1
