ActiveMQ vs NSQ: 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, NSQ is detailed as "A realtime distributed messaging platform". NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.
ActiveMQ and NSQ can be primarily classified as "Message Queue" tools.
"Open source" is the top reason why over 9 developers like ActiveMQ, while over 23 developers mention "It's in golang" as the leading cause for choosing NSQ.
ActiveMQ and NSQ are both open source tools. It seems that NSQ with 15.6K GitHub stars and 2.03K forks on GitHub has more adoption than ActiveMQ with 1.5K GitHub stars and 1.05K GitHub forks.
According to the StackShare community, ActiveMQ has a broader approval, being mentioned in 33 company stacks & 17 developers stacks; compared to NSQ, which is listed in 21 company stacks and 8 developer stacks.
What is ActiveMQ?
What is NSQ?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using ActiveMQ?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with NSQ?
The built-in Gamification that comes with our Playbooks application uses NSQ for work queues and microservice communication.