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

NSQ

125
307
+ 1
143
Redis

49K
37.1K
+ 1
3.9K
Add tool

NSQ vs Redis: What are the differences?

Developers describe NSQ as "A realtime distributed messaging platform". 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. On the other hand, Redis is detailed as "An in-memory database that persists on disk". Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.

NSQ belongs to "Message Queue" category of the tech stack, while Redis can be primarily classified under "In-Memory Databases".

"It's in golang" is the primary reason why developers consider NSQ over the competitors, whereas "Performance" was stated as the key factor in picking Redis.

NSQ and Redis are both open source tools. It seems that Redis with 37.4K GitHub stars and 14.4K forks on GitHub has more adoption than NSQ with 15.6K GitHub stars and 2.03K GitHub forks.

According to the StackShare community, Redis has a broader approval, being mentioned in 3261 company stacks & 1782 developers stacks; compared to NSQ, which is listed in 21 company stacks and 8 developer stacks.

Advice on NSQ and Redis
Pramod Nikam
Co Founder at Usability Designs | 2 upvotes 路 321.6K views
Needs advice
on
Apache ThriftApache ThriftKafkaKafka
and
NSQNSQ

I am looking into IoT World Solution where we have MQTT Broker. This MQTT Broker Sits in one of the Data Center. We are doing a lot of Alert and Alarm related processing on that Data, Currently, we are looking into Solution which can do distributed persistence of log/alert primarily on remote Disk.

Our primary need is to use lightweight where operational complexity and maintenance costs can be significantly reduced. We want to do it on-premise so we are not considering cloud solutions.

We looked into the following alternatives:

Apache Kafka - Great choice but operation and maintenance wise very complex. Rabbit MQ - High availability is the issue, Apache Pulsar - Operational Complexity. NATS - Absence of persistence. Akka Streams - Big learning curve and operational streams.

So we are looking into a lightweight library that can do distributed persistence preferably with publisher and subscriber model. Preferable on JVM stack.

See more
Replies (1)
Naresh Kancharla
Staff Engineer at Nutanix | 4 upvotes 路 318.9K views
Recommends
KafkaKafka

Kafka is best fit here. Below are the advantages with Kafka ACLs (Security), Schema (protobuf), Scale, Consumer driven and No single point of failure.

Operational complexity is manageable with open source monitoring tools.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of NSQ
Pros of Redis
  • 29
    It's in golang
  • 20
    Lightweight
  • 19
    Distributed
  • 18
    Easy setup
  • 16
    High throughput
  • 10
    Publish-Subscribe
  • 7
    Save data if no subscribers are found
  • 7
    Scalable
  • 6
    Open source
  • 5
    Temporarily kept on disk
  • 2
    Simple-to use
  • 1
    Load balanced
  • 1
    Free
  • 1
    Primarily in-memory
  • 1
    Topics and channels concept
  • 879
    Performance
  • 537
    Super fast
  • 510
    Ease of use
  • 441
    In-memory cache
  • 321
    Advanced key-value cache
  • 190
    Open source
  • 179
    Easy to deploy
  • 163
    Stable
  • 152
    Free
  • 120
    Fast
  • 40
    High-Performance
  • 39
    High Availability
  • 34
    Data Structures
  • 32
    Very Scalable
  • 23
    Replication
  • 20
    Great community
  • 19
    Pub/Sub
  • 17
    "NoSQL" key-value data store
  • 14
    Hashes
  • 12
    Sets
  • 10
    Sorted Sets
  • 9
    Lists
  • 8
    BSD licensed
  • 8
    NoSQL
  • 7
    Integrates super easy with Sidekiq for Rails background
  • 7
    Async replication
  • 7
    Bitmaps
  • 6
    Keys with a limited time-to-live
  • 6
    Open Source
  • 5
    Strings
  • 5
    Lua scripting
  • 4
    Hyperloglogs
  • 4
    Awesomeness for Free!
  • 3
    Transactions
  • 3
    Runs server side LUA
  • 3
    outstanding performance
  • 3
    Networked
  • 3
    LRU eviction of keys
  • 3
    Written in ANSI C
  • 3
    Feature Rich
  • 2
    Performance & ease of use
  • 2
    Data structure server
  • 1
    Simple
  • 1
    Channels concept
  • 1
    Scalable
  • 1
    Temporarily kept on disk
  • 1
    Dont save data if no subscribers are found
  • 1
    Automatic failover
  • 1
    Easy to use
  • 1
    Existing Laravel Integration
  • 1
    Object [key/value] size each 500 MB

Sign up to add or upvote prosMake informed product decisions

Cons of NSQ
Cons of Redis
  • 1
    Get NSQ behavior out of Kafka but not inverse
  • 1
    Long term persistence
  • 1
    HA
  • 14
    Cannot query objects directly
  • 2
    No secondary indexes for non-numeric data types
  • 1
    No WAL

Sign up to add or upvote consMake informed product decisions

What is 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.

What is Redis?

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

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

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

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

What tools integrate with NSQ?
What tools integrate with Redis?
    No integrations found

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Nov 20 2019 at 3:38AM

    OneSignal

    PostgreSQLRedisRuby+8
    8
    4160
    Jun 6 2019 at 5:11PM

    AppSignal

    RedisRubyKafka+9
    15
    1255
    GitHubDockerReact+17
    35
    32607
    What are some alternatives to NSQ and Redis?
    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.
    NATS
    Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems.
    gRPC
    gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking...
    MQTT
    It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
    See all alternatives