Sandglass vs Starling: What are the differences?
Developers describe Sandglass as "Distributed, scalable, persistent time-sorted message queue". A distributed, horizontally scalable, persistent, time ordered message queue. Developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue. On the other hand, Starling is detailed as "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.
Sandglass and Starling belong to "Message Queue" category of the tech stack.
Some of the features offered by Sandglass are:
- Horizontal scalability
- Highly available
- Persistent storage
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
Sandglass and Starling are both open source tools. It seems that Sandglass with 1.52K GitHub stars and 40 forks on GitHub has more adoption than Starling with 468 GitHub stars and 63 GitHub forks.