Need advice about which tool to choose?Ask the StackShare community!
Azure Service Bus vs MSMQ: What are the differences?
Introduction
This Markdown code provides a comparison between Azure Service Bus and MSMQ, highlighting the key differences between the two messaging services.
Scalability: Azure Service Bus is a cloud-based messaging service that offers higher scalability compared to MSMQ, which is limited to the capabilities and resources of a single machine. With Azure Service Bus, users can handle large numbers of messages and scale their applications as needed.
Message Size: Azure Service Bus allows larger message sizes compared to MSMQ. While MSMQ has a limit of 4 MB per message, Azure Service Bus supports message sizes of up to 1 MB for the Standard tier and 100 MB for the Premium tier.
Protocol Support: Azure Service Bus supports multiple protocols such as AMQP, MQTT, and HTTPS, providing flexibility in communication options. On the other hand, MSMQ primarily uses the TCP/IP protocol for communication, limiting the protocol options available.
Cross-Platform Compatibility: Azure Service Bus is designed to work seamlessly with various platforms and programming languages, including .NET, Java, Node.js, and more. MSMQ, on the other hand, is primarily tailored for Windows-based systems and may not have the same level of compatibility with other platforms.
Message Persistence: In Azure Service Bus, messages are persisted by default, ensuring reliable delivery even if the receiver is not immediately available. MSMQ, by default, only offers in-memory message delivery, which means that messages may be lost if the receiver is not active or the machine is restarted.
Azure Integration: Azure Service Bus is tightly integrated with other Azure services, providing easy integration and seamless communication between different components of cloud-based applications. MSMQ, being a Windows-based messaging service, does not have the same level of integration capabilities with Azure services.
In summary, Azure Service Bus offers greater scalability, supports larger message sizes, provides more protocol options, offers better cross-platform compatibility, ensures message persistence by default, and seamlessly integrates with other Azure services compared to MSMQ.
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 MSMQ
- Easy to learn2
- Cloud not needed1
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
Cons of MSMQ
- Windows dependency1
