NSQ
nsq.io
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What NSQ is
NSQ is a free, open-source real-time distributed messaging platform for streaming and job-oriented workloads. It uses decentralized topologies that scale horizontally without a centralized broker or single point of failure. Topics can multicast to channels, while each channel distributes messages among its consumers. Delivery is at least once, so duplicates are possible and consumers should use idempotent processing or de-duplication. Message order is not guaranteed. Messages stay mainly in memory by default, with configurable disk overflow, and NSQ has no built-in replication. nsqlookupd discovers producers at runtime, and nsqadmin provides web-based cluster inspection and administration. TCP supports publishing and push consumption; HTTP handles statistics, administrative actions, and publishing without a client library. TLS is available for client connections. Official libraries are listed for Go, Python, and JavaScript, with community libraries for other languages. Prebuilt binaries and an official Docker image are provided.
Who it suits
NSQ suits teams building self-hosted distributed messaging for high-throughput streams or lower-throughput jobs. It is also usable for RPC, although the maker says it was not designed for that use.
Good to know, and what to watch
- Free and open source
- Horizontally scalable topology
- TCP and HTTP interfaces
- Runtime producer discovery
- Official Docker image
- At-least-once delivery can duplicate messages
- Message order is not guaranteed
- No built-in replication
- Messages default to memory storage
The verdict
NSQ provides brokerless distributed messaging with flexible topic and channel routing. Teams must design for duplicate, unordered delivery and the absence of built-in replication.
What the maker publishes
- Admin interface
- The nsqadmin web service provides real-time instrumentation and cluster administration. source
- Architecture
- NSQ supports decentralized, horizontally scalable topologies without a centralized broker or single point of failure. source
- Client libraries
- The project lists official Go, Python, and JavaScript client libraries, along with community libraries for other languages. source
- Client libraries
- The maker lists official client libraries for Go, Python, JavaScript, and C, alongside community libraries for other languages. source
- Delivery
- Messages are delivered at least once, so consumers may receive duplicates and should use idempotent processing or de-duplication. source
- Deployment
- The project offers prebuilt binaries for Linux, Darwin, FreeBSD, and Windows, plus an official Docker image. source
- Discovery and admin
- nsqlookupd provides runtime producer discovery, and nsqadmin provides a web interface for inspecting and administering a cluster. source
- Distribution
- NSQ supports distributed topologies without a single point of failure and scales horizontally without brokers. source
- Integrations
- NSQ can send realtime instrumentation to StatsD and nsqadmin can use Graphite for charts when StatsD is enabled. source
- Integrations
- NSQ can send real-time instrumentation to statsd; nsqadmin can use Graphite for charts when statsd is enabled. source
- Message delivery
- NSQ provides at-least-once delivery, so consumers should expect possible duplicates and deduplicate messages or use idempotent operations. source
- Message routing
- NSQ supports both multicast-style routing from topics to channels and load-balanced delivery from channels to consumers. source
- Ordering
- Messages are not guaranteed to arrive in order. source
- Ordering limit
- Consumers cannot rely on messages being delivered in order. source
- Platforms
- Pre-built binaries are available for Linux, Darwin, FreeBSD, and Windows, and the maker documents Docker deployment. source
- Protocol
- The TCP protocol supports publishing and push-based consumption, and the system also provides an HTTP interface for stats, admin actions, and publishing. source
- Publishing
- Messages can be published through HTTP endpoints without a client library. source
- Purpose
- NSQ is a realtime distributed messaging platform. source
- Routing
- NSQ supports multicast delivery from topics to channels and distributes each channel’s messages among its consumers. source
- RPC limitation
- NSQ can be used for RPC, but the maker says it was not designed for that use case. source
- Security
- NSQ supports transport-layer security (TLS) for client connections. source
- Security
- NSQ supports transport layer security (TLS). source
- Storage limit
- Messages are primarily held in memory by default, with configurable disk overflow; NSQ has no built-in replication. source
- Storage limit
- Messages are not durable by default; NSQ has no built-in replication, though queued messages can be written to disk after the configured in-memory threshold. source
Checked against the maker's pages on 10 Oct 2026.