Need advice about which tool to choose?Ask the StackShare community!

Disque

11
25
+ 1
0
Mosca

16
43
+ 1
0
Add tool

Disque vs Mosca: What are the differences?

  1. Protocol Support: Disque supports the Redis protocol, allowing clients using the Redis protocol to interact with Disque seamlessly. On the other hand, Mosca is a standalone MQTT broker that works exclusively with the MQTT protocol, providing support for publishing and subscribing to messages.
  2. Message Broker Type: Disque is a distributed message broker system designed for high-performance message queuing, whereas Mosca is a lightweight and low-level MQTT broker intended for IoT and real-time communication applications.
  3. Scalability: Disque is designed to be highly scalable, supporting millions of messages per second across multiple nodes for horizontal scalability. In contrast, Mosca is more suitable for smaller-scale applications due to its focus on lightweight communication for IoT devices.
  4. Message Routing: Disque uses a round-robin message distribution mechanism to ensure even load balancing across nodes, while Mosca uses the publish/subscribe pattern inherent in the MQTT protocol for message routing between clients.
  5. Persistence: Disque supports persistence to disk for message durability, ensuring that messages are not lost in case of system failures. Mosca, on the other hand, relies on its clients to handle message persistence if necessary, making it more lightweight but potentially less reliable in certain use cases.

In Summary, Disque and Mosca differ in protocol support, message broker type, scalability, message routing, and persistence mechanisms.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
- No public GitHub repository available -

What is Disque?

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.

What is Mosca?

A Node.js MQTT broker, which can be used as a Standalone Service or embedded in another Node.js application.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Disque?
What companies use Mosca?
See which teams inside your own company are using Disque or Mosca.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Disque?
What tools integrate with Mosca?
    No integrations found
    What are some alternatives to Disque and Mosca?
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    Kafka
    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
    Amazon SQS
    Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.
    Celery
    Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
    ActiveMQ
    Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
    See all alternatives