NSQ vs Starling: What are the differences?
NSQ: A realtime distributed messaging platform. 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; 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.
NSQ and Starling can be primarily classified as "Message Queue" tools.
Some of the features offered by NSQ are:
- support distributed topologies with no SPOF
- horizontally scalable (no brokers, seamlessly add more nodes to the cluster)
- low-latency push based message delivery (performance)
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
NSQ and Starling are both open source tools. NSQ with 15.6K GitHub stars and 2.03K forks on GitHub appears to be more popular than Starling with 468 GitHub stars and 63 GitHub forks.