Disque vs Starling: What are the differences?

Disque: In-memory, distributed job queue. Disque is an ongoing experiment to build a distributed, in-memory, message broker. Its goal is to capture the essence of the "Redis as a jobs queue" use case, which is usually implemented using blocking list operations, and move it into an ad-hoc, self-contained, scalable, and fault tolerant design, with simple to understand properties and guarantees, but still resembling Redis in terms of simplicity, performance, and implementation as a C non-blocking networked server; 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.

Disque and Starling can be primarily classified as "Message Queue" tools.

Disque and Starling are both open source tools. Disque with 7.37K GitHub stars and 516 forks on GitHub appears to be more popular than Starling with 468 GitHub stars and 63 GitHub forks.