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. DoctorKafka vs RSMQ

DoctorKafka vs RSMQ

OverviewComparisonAlternatives

Overview

RSMQ
RSMQ
Stacks4
Followers87
Votes6
GitHub Stars1.8K
Forks120
DoctorKafka
DoctorKafka
Stacks4
Followers17
Votes0

DoctorKafka vs RSMQ: What are the differences?

Developers describe DoctorKafka as "A service for Kafka cluster auto healing and workload balancing". DoctorKafka can automatically detect broker failure and reassign the workload on the failed nodes to other nodes. DoctorKafka can also perform load balancing based on topic partitions's network usage, and makes sure that broker network usage does not exceed the defined settings. On the other hand, RSMQ is detailed as "A lightweight message queue for Node.js that requires no dedicated queue server. Just a Redis server". tl;dr: If you run a Redis server and currently use Amazon SQS or a similar message queue you might as well use this fast little replacement. Using a shared Redis server multiple Node.js processes can send / receive messages.

DoctorKafka and RSMQ can be categorized as "Message Queue" tools.

DoctorKafka and RSMQ are both open source tools. It seems that RSMQ with 1.07K GitHub stars and 78 forks on GitHub has more adoption than DoctorKafka with 488 GitHub stars and 68 GitHub forks.

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

RSMQ
RSMQ
DoctorKafka
DoctorKafka

tl;dr: If you run a Redis server and currently use Amazon SQS or a similar message queue you might as well use this fast little replacement. Using a shared Redis server multiple Node.js processes can send / receive messages.

DoctorKafka can automatically detect broker failure and reassign the workload on the failed nodes to other nodes. DoctorKafka can also perform load balancing based on topic partitions's network usage, and makes sure that broker network usage does not exceed the defined settings.

Lightweight: Just Redis and ~500 lines of javascript.;Guaranteed delivery of a message to exactly one recipient within a messages visibility timeout.;Received messages that are not deleted will reappear after the visibility timeout.;Test coverage;Optional RESTful interface via rest-rsmq
-
Statistics
GitHub Stars
1.8K
GitHub Stars
-
GitHub Forks
120
GitHub Forks
-
Stacks
4
Stacks
4
Followers
87
Followers
17
Votes
6
Votes
0
Pros & Cons
Pros
  • 2
    Simple, does one thing well
  • 1
    Written in TypeScript
  • 1
    Written in Coffeescript
  • 1
    Backed by Redis
  • 1
    Comes with a visibility timeout feature similar to AWS
No community feedback yet
Integrations
Redis
Redis
Kafka
Kafka

What are some alternatives to RSMQ, DoctorKafka?

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