Disque vs WCF: What are the differences?
Developers describe Disque as "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. On the other hand, WCF is detailed as "A runtime and a set of APIs for building connected, service-oriented applications". It is a framework for building service-oriented applications. Using this, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application.
Disque belongs to "Message Queue" category of the tech stack, while WCF can be primarily classified under "Realtime Backend / API".
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.