Azure Service Bus vs NServiceBus

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

Azure Service Bus

194
459
+ 1
7
NServiceBus

51
122
+ 1
2
Add tool

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.

Advice on Azure Service Bus and NServiceBus
André Almeida
Technology Manager at GS1 Portugal - Codipor · | 5 upvotes · 294.9K 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 NServiceBus
  • 4
    Easy Integration with .Net
  • 2
    Cloud Native
  • 1
    Use while high messaging need
  • 1
    Brings on-prem issues to the cloud
  • 1
    Not as good as alternatives, good job security

Sign up to add or upvote prosMake informed product decisions

Cons of Azure Service Bus
Cons of NServiceBus
  • 1
    Observability of messages in the queue is lacking
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    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 NServiceBus?

    Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.

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

    What companies use Azure Service Bus?
    What companies use NServiceBus?
    See which teams inside your own company are using Azure Service Bus or NServiceBus.
    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 NServiceBus?
      No integrations found
      What are some alternatives to Azure Service Bus and NServiceBus?
      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.
      Amazon SQS
      Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.
      See all alternatives