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

RSMQ vs Samza

OverviewComparisonAlternatives

Overview

Samza
Samza
Stacks24
Followers62
Votes0
GitHub Stars832
Forks333
RSMQ
RSMQ
Stacks4
Followers87
Votes6
GitHub Stars1.8K
Forks120

RSMQ vs Samza: What are the differences?

Developers describe RSMQ 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. On the other hand, Samza is detailed as "A distributed stream processing framework". Samza allows you to build stateful applications that process data in real-time from multiple sources including Apache Kafka.

RSMQ and Samza belong to "Message Queue" category of the tech stack.

Some of the features offered by RSMQ are:

  • 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.

On the other hand, Samza provides the following key features:

  • HIGH PERFORMANCE
  • HORIZONTALLY SCALABLE
  • EASY TO OPERATE

RSMQ and Samza are both open source tools. RSMQ with 1.1K GitHub stars and 83 forks on GitHub appears to be more popular than Samza with 565 GitHub stars and 243 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

Samza
Samza
RSMQ
RSMQ

It allows you to build stateful applications that process data in real-time from multiple sources including Apache Kafka.

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.

HIGH PERFORMANCE; HORIZONTALLY SCALABLE; EASY TO OPERATE; WRITE ONCE, RUN ANYWHERE; PLUGGABLE ARCHITECTURE
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
832
GitHub Stars
1.8K
GitHub Forks
333
GitHub Forks
120
Stacks
24
Stacks
4
Followers
62
Followers
87
Votes
0
Votes
6
Pros & Cons
No community feedback yet
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
Integrations
Presto
Presto
Datadog
Datadog
Woopra
Woopra
Redis
Redis

What are some alternatives to Samza, RSMQ?

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