StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. Apache RocketMQ vs Disque

Apache RocketMQ vs Disque

OverviewComparisonAlternatives

Overview

Disque
Disque
Stacks11
Followers25
Votes0
GitHub Stars8.1K
Forks537
Apache RocketMQ
Apache RocketMQ
Stacks48
Followers200
Votes8

Apache RocketMQ vs Disque: What are the differences?

  1. Message Broker Type: Apache RocketMQ is a distributed message broker system whereas Disque is a distributed message broker and job queue system.
  2. Persistence Mechanism: Apache RocketMQ supports persistent and non-persistent message delivery while Disque only supports persistent message storage.
  3. Message Durability: RocketMQ guarantees message delivery in the event of system failures, but Disque doesn't provide such a guarantee for every message.
  4. Message Ordering: RocketMQ ensures strict message ordering within the same message queue, ensuring sequential processing. Disque may not maintain strict ordering for messages.
  5. Messaging Protocols: Apache RocketMQ supports multiple messaging protocols like AMQP, STOMP, MQTT, while Disque focuses primarily on supporting the Redis protocol for message exchange.
  6. Scalability: RocketMQ allows for horizontal scalability by adding more nodes in a cluster, providing higher throughput and fault tolerance. Disque has limited scalability compared to RocketMQ due to its design approach.

In Summary, Apache RocketMQ and Disque differ in terms of message broker type, persistence mechanism, message durability, message ordering, supported messaging protocols, and scalability.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Disque
Disque
Apache RocketMQ
Apache RocketMQ

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.

Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability.

Statistics
GitHub Stars
8.1K
GitHub Stars
-
GitHub Forks
537
GitHub Forks
-
Stacks
11
Stacks
48
Followers
25
Followers
200
Votes
0
Votes
8
Pros & Cons
No community feedback yet
Pros
  • 2
    Million-level message accumulation capacity in a single
  • 2
    Support tracing message and transactional message
  • 1
    Feature-rich administrative dashboard for configuration
  • 1
    Low latency
  • 1
    High throughput messaging
Integrations
No integrations available
Docker
Docker

What are some alternatives to Disque, Apache RocketMQ?

Kafka

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

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.

Amazon SQS

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.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

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.

ZeroMQ

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase