ActiveMQ vs ZeroMQ: 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; ZeroMQ: Fast, lightweight messaging library that allows you to design complex communication system without much effort. 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.
ActiveMQ and ZeroMQ can be primarily classified as "Message Queue" tools.
"Open source" is the top reason why over 9 developers like ActiveMQ, while over 17 developers mention "Fast" as the leading cause for choosing ZeroMQ.
ActiveMQ and ZeroMQ are both open source tools. ZeroMQ with 5.33K GitHub stars and 1.57K forks on GitHub appears to be more popular than ActiveMQ with 1.5K GitHub stars and 1.05K GitHub forks.
Intuit, SoFi, and Bench are some of the popular companies that use ActiveMQ, whereas ZeroMQ is used by Binary.com, GrowSumo, and Runbook. ActiveMQ has a broader approval, being mentioned in 33 company stacks & 17 developers stacks; compared to ZeroMQ, which is listed in 35 company stacks and 12 developer stacks.
What is ActiveMQ?
What is ZeroMQ?
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
Our platform is based on interconnected services with a custom RPC protocol based on ZeroMQ and inspired by ZeroMQs LPP/MDP protocols.
Remote broker and local client for incoming data feeds. Local broker for republishing data feeds to other systems.