Mosca vs Starling: What are the differences?

Developers describe Mosca as "A Node.js MQTT broker". A Node.js MQTT broker, which can be used as a Standalone Service or embedded in another Node.js application. 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.

Mosca and Starling can be categorized as "Message Queue" tools.

Some of the features offered by Mosca are:

• MQTT 3.1 and 3.1.1 compliant
• QoS 0 and QoS 1
• Various storage options for QoS 1 offline packets, and subscriptions

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

Mosca and Starling are both open source tools. It seems that Mosca with 2.84K GitHub stars and 501 forks on GitHub has more adoption than Starling with 468 GitHub stars and 63 GitHub forks.