ActiveMQ vs ejabberd

Overview

ActiveMQ

Stacks879

Followers1.3K

Votes77

GitHub Stars2.4K

Forks1.5K

ejabberd

Stacks33

Followers48

Votes0

GitHub Stars6.5K

Forks1.5K

ActiveMQ vs ejabberd: 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, ejabberd is detailed as "A scalable and robust instant messaging server". It is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance.

ActiveMQ and ejabberd can be categorized as "Message Queue" tools.

ActiveMQ and ejabberd are both open source tools. ejabberd with 4.18K GitHub stars and 1.25K forks on GitHub appears to be more popular than ActiveMQ with 1.53K GitHub stars and 1.06K GitHub forks.

Intuit, Wix, and SoFi are some of the popular companies that use ActiveMQ, whereas ejabberd is used by AppScale Systems, KongHack Inc., and UrbanClap. ActiveMQ has a broader approval, being mentioned in 52 company stacks & 120 developers stacks; compared to ejabberd, which is listed in 5 company stacks and 3 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

ActiveMQ	ejabberd
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.	It is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance.
Protect your data & Balance your Load; Easy enterprise integration patterns; Flexible deployment	Cross-platform; Administrator-friendly; Internationalized; Fault-tolerant
Statistics
GitHub Stars 2.4K	GitHub Stars 6.5K
GitHub Forks 1.5K	GitHub Forks 1.5K
Stacks 879	Stacks 33
Followers 1.3K	Followers 48
Votes 77	Votes 0
Pros & Cons
Pros 18 Easy to use 14 Open source 13 Efficient 10 JMS compliant 6 High Availability Cons 1 Low resilience to exceptions and interruptions 1 ONLY Vertically Scalable 1 Support 1 Difficult to scale	No community feedback yet
Integrations
No integrations available	PostgreSQL Linux MySQL Mac OS X

What are some alternatives to ActiveMQ, ejabberd?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

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.

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.

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

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.

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.