Need advice about which tool to choose?Ask the StackShare community!
ActiveMQ vs Gearman: 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, Gearman is detailed as "A generic application framework to farm out work to other machines or processes". Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.
ActiveMQ and Gearman can be categorized as "Message Queue" tools.
"Open source" is the primary reason why developers consider ActiveMQ over the competitors, whereas "Free" was stated as the key factor in picking Gearman.
ActiveMQ is an open source tool with 1.5K GitHub stars and 1.05K GitHub forks. Here's a link to ActiveMQ's open source repository on GitHub.
According to the StackShare community, ActiveMQ has a broader approval, being mentioned in 33 company stacks & 17 developers stacks; compared to Gearman, which is listed in 19 company stacks and 5 developer stacks.
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 Gearman
- Ease of use and very simple APIs11
- Free11
- Polyglot6
- No single point of failure5
- Scalable3
- High-throughput3
- Foreground & background processing2
- Very fast2
- Different Programming Languages Channel1
- Many supported programming languages1
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