Need advice about which tool to choose?Ask the StackShare community!
ActiveMQ vs DistributedLog: 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, DistributedLog is detailed as "High-performance replicated log service, by Twitter". DistributedLog (DL) is a high-performance, replicated log service, offering durability, replication and strong consistency as essentials for building reliable distributed systems.
ActiveMQ and DistributedLog can be categorized as "Message Queue" tools.
ActiveMQ and DistributedLog are both open source tools. DistributedLog with 2.25K GitHub stars and 283 forks on GitHub appears to be more popular than ActiveMQ with 1.5K GitHub stars and 1.05K GitHub forks.
Pros of ActiveMQ
- Easy to use18
- Open source14
- Efficient13
- JMS compliant10
- High Availability6
- Scalable5
- Distributed Network of brokers3
- Persistence3
- Support XA (distributed transactions)3
- Docker delievery1
- Highly configurable1
- RabbitMQ0
Pros of DistributedLog
Sign up to add or upvote prosMake informed product decisions
Cons of ActiveMQ
- ONLY Vertically Scalable1
- Support1
- Low resilience to exceptions and interruptions1
- Difficult to scale1