StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. DistributedLog vs ejabberd

DistributedLog vs ejabberd

OverviewComparisonAlternatives

Overview

ejabberd
ejabberd
Stacks33
Followers48
Votes0
GitHub Stars6.5K
Forks1.5K
DistributedLog
DistributedLog
Stacks21
Followers39
Votes0

DistributedLog vs ejabberd: What are the differences?

Developers describe DistributedLog 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. 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.

DistributedLog and ejabberd belong to "Message Queue" category of the tech stack.

Some of the features offered by DistributedLog are:

  • High Performance
  • Durable and Consistent
  • Efficient Fan-in and Fan-out

On the other hand, ejabberd provides the following key features:

  • Cross-platform
  • Administrator-friendly
  • Internationalized

DistributedLog and ejabberd are both open source tools. It seems that ejabberd with 4.18K GitHub stars and 1.25K forks on GitHub has more adoption than DistributedLog with 2.25K GitHub stars and 283 GitHub forks.

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)
or
Manual

Detailed Comparison

ejabberd
ejabberd
DistributedLog
DistributedLog

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.

DistributedLog (DL) is a high-performance, replicated log service, offering durability, replication and strong consistency as essentials for building reliable distributed systems.

Cross-platform; Administrator-friendly; Internationalized; Fault-tolerant
High Performance;Durable and Consistent;Efficient Fan-in and Fan-out;Various Workloads;Multi Tenant;Layered Architecture
Statistics
GitHub Stars
6.5K
GitHub Stars
-
GitHub Forks
1.5K
GitHub Forks
-
Stacks
33
Stacks
21
Followers
48
Followers
39
Votes
0
Votes
0
Integrations
PostgreSQL
PostgreSQL
Linux
Linux
MySQL
MySQL
Mac OS X
Mac OS X
No integrations available

What are some alternatives to ejabberd, DistributedLog?

Kafka

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

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

Celery

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

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

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

ActiveMQ

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

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

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

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

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.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase