DistributedLog vs Starling: What are the differences?
DistributedLog: 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; Starling: A light weight server for reliable distributed message passing. Starling is a powerful but simple messaging server that enables reliable distributed queuing with an absolutely minimal overhead. It speaks the MemCache protocol for maximum cross-platform compatibility. Any language that speaks MemCache can take advantage of Starling's queue facilities.
DistributedLog and Starling can be primarily classified as "Message Queue" tools.
Some of the features offered by DistributedLog are:
- High Performance
- Durable and Consistent
- Efficient Fan-in and Fan-out
On the other hand, Starling provides the following key features:
- Written by Blaine Cook at Twitter
- Starling is a Message Queue Server based on MemCached
- Written in Ruby
DistributedLog and Starling are both open source tools. DistributedLog with 2.25K GitHub stars and 283 forks on GitHub appears to be more popular than Starling with 468 GitHub stars and 63 GitHub forks.