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

ActiveMQ

451
1.1K
+ 1
75
IBM MQ

87
128
+ 1
9
Add tool

ActiveMQ vs IBM MQ: 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, IBM MQ is detailed as "Enterprise-grade messaging middleware". 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.

ActiveMQ and IBM MQ belong to "Message Queue" category of the tech stack.

ActiveMQ is an open source tool with 1.51K GitHub stars and 1.05K GitHub forks. Here's a link to ActiveMQ's open source repository on GitHub.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of ActiveMQ
Pros of IBM MQ
  • 17
    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
  • 3
    Reliable for banking transactions
  • 2
    Useful for big enteprises
  • 2
    Secure
  • 1
    Many deployment options (containers, cloud, VM etc)
  • 1
    High Availability

Sign up to add or upvote prosMake informed product decisions

Cons of ActiveMQ
Cons of IBM MQ
  • 1
    Support
  • 1
    Low resilience to exceptions and interruptions
  • 1
    Difficult to scale
  • 2
    Cost

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 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.

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

What companies use ActiveMQ?
What companies use IBM MQ?
See which teams inside your own company are using ActiveMQ or IBM MQ.
Sign up for Private StackShareLearn More

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

What tools integrate with ActiveMQ?
What tools integrate with IBM MQ?

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

Blog Posts

What are some alternatives to ActiveMQ and IBM MQ?
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.
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.
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