Need advice about which tool to choose?Ask the StackShare community!
ActiveMQ vs Azure Service Bus: What are the differences?
Developers describe ActiveMQ as "A message broker written in Java together with a full JMS client". Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License. On the other hand, Azure Service Bus is detailed 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.
ActiveMQ and Azure Service Bus can be primarily classified as "Message Queue" tools.
ActiveMQ is an open source tool with 1.53K GitHub stars and 1.06K GitHub forks. Here's a link to ActiveMQ's open source repository on GitHub.
According to the StackShare community, ActiveMQ has a broader approval, being mentioned in 52 company stacks & 120 developers stacks; compared to Azure Service Bus, which is listed in 11 company stacks and 8 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 ActiveMQ
- Easy to use18
- Open source14
- Efficient13
- JMS compliant10
- High Availability6
- Scalable5
- Distributed Network of brokers3
- Persistence3
- Support XA (distributed transactions)3
- Docker delievery1
- Highly configurable1
- RabbitMQ0
Pros of Azure Service Bus
- Easy Integration with .Net4
- Cloud Native2
- Use while high messaging need1
Sign up to add or upvote prosMake informed product decisions
Cons of ActiveMQ
- ONLY Vertically Scalable1
- Support1
- Low resilience to exceptions and interruptions1
- Difficult to scale1
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
Sign up to add or upvote consMake informed product decisions
What is ActiveMQ?
What is Azure Service Bus?
Need advice about which tool to choose?Ask the StackShare community!
What companies use ActiveMQ?
What companies use Azure Service Bus?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+35