Disque vs IronMQ: 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; IronMQ: Message Queue for any deployment. An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

Disque and IronMQ belong to "Message Queue" category of the tech stack.

Disque is an open source tool with 7.37K GitHub stars and 516 GitHub forks. Here's a link to Disque's open source repository on GitHub.