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

ActiveMQ

652
1.2K
+ 1
76
Azure Service Bus

428
442
+ 1
7
Add tool

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.

Advice on ActiveMQ and Azure Service Bus
André Almeida
Technology Manager at GS1 Portugal - Codipor · | 5 upvotes · 274.4K 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 ActiveMQ
Pros of Azure Service Bus
  • 18
    Easy to use
  • 14
    Open source
  • 13
    Efficient
  • 10
    JMS compliant
  • 6
    High Availability
  • 5
    Scalable
  • 3
    Support XA (distributed transactions)
  • 3
    Persistence
  • 2
    Distributed Network of brokers
  • 1
    Highly configurable
  • 1
    Docker delievery
  • 0
    RabbitMQ
  • 4
    Easy Integration with .Net
  • 2
    Cloud Native
  • 1
    Use while high messaging need

Sign up to add or upvote prosMake informed product decisions

Cons of ActiveMQ
Cons of Azure Service Bus
  • 1
    Support
  • 1
    Low resilience to exceptions and interruptions
  • 1
    Difficult to scale
  • 1
    Observability of messages in the queue is lacking

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is ActiveMQ?

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.

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.

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

What companies use ActiveMQ?
What companies use Azure Service Bus?
See which teams inside your own company are using ActiveMQ or Azure Service Bus.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with ActiveMQ?
What tools integrate with Azure Service Bus?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to ActiveMQ and Azure 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.
Apollo
Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.
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.
ZeroMQ
The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.
See all alternatives