Kestrel vs Sandglass: What are the differences?
Developers describe Kestrel as "Simple, distributed message queue system". Kestrel is based on Blaine Cook's "starling" simple, distributed message queue, with added features and bulletproofing, as well as the scalability offered by actors and the JVM. On the other hand, Sandglass is detailed 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.
Kestrel and Sandglass can be primarily classified as "Message Queue" tools.
Some of the features offered by Kestrel are:
- Written by Robey Pointer
- Starling clone written in Scala (a port of Starling from Ruby to Scala)
- Queues are stored in memory, but logged on disk
On the other hand, Sandglass provides the following key features:
- Horizontal scalability
- Highly available
- Persistent storage
Kestrel and Sandglass are both open source tools. It seems that Kestrel with 2.8K GitHub stars and 326 forks on GitHub has more adoption than Sandglass with 1.52K GitHub stars and 40 GitHub forks.