Home
Application and Data
Data Stores
Message Queue

NSQ vs Sandglass

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

NSQ
140
349
+ 1
148
Sandglass
1
6
+ 1
0
Add tool

NSQ vs Sandglass: What are the differences?

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

What is Sandglass? Distributed, scalable, persistent time-sorted message queue. A distributed, horizontally scalable, persistent, time ordered message queue. Developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue.

NSQ and Sandglass can be categorized as "Message Queue" tools.

Some of the features offered by NSQ are:

  • support distributed topologies with no SPOF
  • horizontally scalable (no brokers, seamlessly add more nodes to the cluster)
  • low-latency push based message delivery (performance)

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

  • Horizontal scalability
  • Highly available
  • Persistent storage

NSQ and Sandglass are both open source tools. NSQ with 15.6K GitHub stars and 2.03K forks on GitHub appears to be more popular than Sandglass with 1.52K GitHub stars and 40 GitHub forks.

Advice on NSQ and Sandglass
Pramod Nikam
Co Founder at Usability Designs · | 2 upvotes · 520.2K 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 · 517.6K views
Recommends
on
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 Sandglass
  • 29
    It's in golang
  • 20
    Distributed
  • 20
    Lightweight
  • 18
    Easy setup
  • 17
    High throughput
  • 11
    Publish-Subscribe
  • 8
    Scalable
  • 8
    Save data if no subscribers are found
  • 6
    Open source
  • 5
    Temporarily kept on disk
  • 2
    Simple-to use
  • 1
    Free
  • 1
    Topics and channels concept
  • 1
    Load balanced
  • 1
    Primarily in-memory
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of NSQ
    Cons of Sandglass
    • 1
      Long term persistence
    • 1
      Get NSQ behavior out of Kafka but not inverse
    • 1
      HA
      Be the first to leave a con

      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 Sandglass?

      A distributed, horizontally scalable, persistent, time ordered message queue. Developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue.

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

      Jobs that mention NSQ and Sandglass as a desired skillset
      Senior Software Engineer, Big Data
      Pinterest
      San Francisco, CA, US; , CA, US
      View Job Details
      DreamTrinoAirflow+11
      Staff Software Engineer - Site Reliability
      Pinterest
      Toronto, ON, CA
      View Job Details
      SpeedDreamLinux+20
      Manager II, Engineering - Big Data Query Platform
      Pinterest
      San Francisco, CA, US; , US
      View Job Details
      DreamTrinoYarn+7
      Staff Software Engineer, Internal LLM Tooling
      Pinterest
      Toronto, ON, CA
      View Job Details
      LLMDreamTypeScript+8
      Backend Engineer, Data Pipeline
      LaunchDarkly
      Oakland, California, United States
      View Job Details
      EscapeGoogleage+10
      What companies use NSQ?
      What companies use Sandglass?
        No companies found
        See which teams inside your own company are using NSQ or Sandglass.
        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 Sandglass?

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

        What are some alternatives to NSQ and Sandglass?
        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.
        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.
        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...
        See all alternatives

        Related Comparisons

        Kafka vs NSQ vs RabbitMQKafka vs NSQAmazon SQS vs NSQNSQ vs RabbitMQ vs ZeroMQApache RocketMQ vs Kafka vs NSQ

        Trending Comparisons

        Django vs Laravel vs Node.jsBootstrap vs Foundation vs Material-UINode.js vs Spring BootFlyway vs LiquibaseAWS CodeCommit vs Bitbucket vs GitHub

        Top Comparisons

        Bootstrap vs MaterializeHipChat vs Mattermost vs SlackBitbucket vs GitHub vs GitLabPostman vs Swagger UI