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

ActiveMQ

446
1.1K
+ 1
75
MQTT

337
369
+ 1
4
Add tool

ActiveMQ vs MQTT: What are the differences?

ActiveMQ: 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; MQTT: A machine-to-machine Internet of Things connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.

ActiveMQ and MQTT can be primarily classified as "Message Queue" tools.

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.

Intuit, Wix, and SoFi are some of the popular companies that use ActiveMQ, whereas MQTT is used by Pubu, Jaumo, and Danale Inc. ActiveMQ has a broader approval, being mentioned in 33 company stacks & 17 developers stacks; compared to MQTT, which is listed in 12 company stacks and 6 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of ActiveMQ
Pros of MQTT
  • 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
  • 2
    Varying levels of Quality of Service to fit a range of
  • 1
    Very easy to configure and use with open source tools
  • 1
    Lightweight with a relatively small data footprint

Sign up to add or upvote prosMake informed product decisions

Cons of ActiveMQ
Cons of MQTT
  • 1
    Support
  • 1
    Low resilience to exceptions and interruptions
  • 1
    Difficult to scale
  • 1
    Easy to configure in an unsecure manner

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

It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.

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

What companies use ActiveMQ?
What companies use MQTT?
See which teams inside your own company are using ActiveMQ or MQTT.
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 MQTT?

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

Blog Posts

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