What is DistributedLog?
DistributedLog (DL) is a high-performance, replicated log service, offering durability, replication and strong consistency as essentials for building reliable distributed systems.
DistributedLog is a tool in the Message Queue category of a tech stack.
DistributedLog is an open source tool with 2.3K GitHub stars and 289 GitHub forks. Here’s a link to DistributedLog's open source repository on GitHub
Who uses DistributedLog?
13 developers on StackShare have stated that they use DistributedLog.
Why developers like DistributedLog?
Here’s a list of reasons why companies and developers use DistributedLog
Be the first to leave a pro
- High Performance
- Durable and Consistent
- Efficient Fan-in and Fan-out
- Various Workloads
- Multi Tenant
- Layered Architecture
DistributedLog Alternatives & Comparisons
What are some alternatives to DistributedLog?
See all alternatives
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
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.
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.
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.