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
NSQ
ByNSQNSQ

NSQ

#20in Background Jobs
Discussions1
Followers356
OverviewDiscussions1AdoptionAlternativesIntegrations
Try It

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.

NSQ is a tool in the Background Jobs category of a tech stack.

Key Features

support distributed topologies with no SPOFhorizontally scalable (no brokers, seamlessly add more nodes to the cluster)low-latency push based message delivery (performance)combination load-balanced and multicast style message routingexcel at both streaming (high-throughput) and job oriented (low-throughput) workloadsprimarily in-memory (beyond a high-water mark messages are transparently kept on disk)runtime discovery service for consumers to find producers (nsqlookupd)transport layer security (TLS)data format agnosticfew dependencies (easy to deploy) and a sane, bounded, default configurationsimple TCP protocol supporting client libraries in any languageHTTP interface for stats, admin actions, and producers (no client library needed to publish)integrates with statsd for realtime instrumentationrobust cluster administration interface (nsqadmin)

NSQ Pros & Cons

Pros of NSQ

  • ✓It's in golang
  • ✓Distributed
  • ✓Lightweight
  • ✓Easy setup
  • ✓High throughput
  • ✓Publish-Subscribe
  • ✓Save data if no subscribers are found
  • ✓Scalable
  • ✓Open source
  • ✓Temporarily kept on disk

Cons of NSQ

  • ✗Get NSQ behavior out of Kafka but not inverse
  • ✗HA
  • ✗Long term persistence

NSQ Alternatives & Comparisons

What are some alternatives to NSQ?

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.

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.

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.

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.

MQTT

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.

Try It

Visit Website

Adoption

On StackShare

NSQ Integrations

Benthos are some of the popular tools that integrate with NSQ. Here's a list of all 1 tools that integrate with NSQ.

Benthos
Benthos

NSQ Discussions

Discover why developers choose NSQ. Read real-world technical decisions and stack choices from the StackShare community.

Kenneth Noisewater
Kenneth Noisewater

Jun 27, 2016

Needs adviceonNSQNSQ

The built-in Gamification that comes with our Playbooks application uses NSQ for work queues and microservice communication. NSQ

0 views0
Comments
Companies
32
BDPSSW+26
Developers
109
AFATJD+103