EMQ vs NSQ

Overview

NSQ

Stacks141

Followers356

Votes148

EMQX

Stacks34

Followers109

Votes6

GitHub Stars15.4K

Forks2.4K

NSQ vs EMQ: 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, EMQ is detailed as "The Scalable MQTT Broker for IoT and Mobile Applications". It is fully open source and licensed under the Apache Version 2.0. It implements both MQTT V3.1 and V3.1.1 protocol specifications, and supports MQTT-SN, CoAP, WebSocket, STOMP and SockJS at the same time.

NSQ and EMQ belong to "Message Queue" category of the tech stack.

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, EMQ provides the following key features:

Full MQTT V3.1/3.1.1 Protocol Specifications Support
Easy to Install - Quick Install on Linux, FreeBSD, Mac and Windows
Massively scalable - Scaling to 1 million connections on a single server

NSQ and EMQ are both open source tools. It seems that NSQ with 16.3K GitHub stars and 2.14K forks on GitHub has more adoption than EMQ with 181 GitHub stars and 96 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)

Manual

Advice on NSQ, EMQX

Pramod

Co Founder at Usability Designs

Mar 2, 2020

Needs advice

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.

572k views572k

Comments

Detailed Comparison

NSQ	EMQX
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.	EMQX is a cloud-native, MQTT-based, IoT messaging platform designed for high reliability and massive scale. Licensed under the Apache Version 2.0, EMQX is 100% compliant with MQTT 5.0 and 3.x standard protocol specifications.
support distributed topologies with no SPOF;horizontally scalable (no brokers, seamlessly add more nodes to the cluster);low-latency push based message delivery (performance);combination load-balanced and multicast style message routing;excel at both streaming (high-throughput) and job oriented (low-throughput) workloads;primarily 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 agnostic;few dependencies (easy to deploy) and a sane, bounded, default configuration;simple TCP protocol supporting client libraries in any language;HTTP interface for stats, admin actions, and producers (no client library needed to publish);integrates with statsd for realtime instrumentation;robust cluster administration interface (nsqadmin)	Scale to 100 million concurrent MQTT connections with a single EMQX 5.0 cluster./Licensed under the Apache Version 2.0, 100% compliant with MQTT 5.0 and 3.x standard protocol specifications for better scalability, security, and reliability./Move and process millions of MQTT messages per second in a single broker./Guarantee sub-millisecond latency in message delivery with the soft real-time runtime./Achieve high availability and horizontal scalability with a masterless distributed architecture./Easy to deploy on-premises and in public clouds with Kubernetes Operator and Terraform.
Statistics
GitHub Stars -	GitHub Stars 15.4K
GitHub Forks -	GitHub Forks 2.4K
Stacks 141	Stacks 34
Followers 356	Followers 109
Votes 148	Votes 6
Pros & Cons
Pros 29 It's in golang 20 Distributed 20 Lightweight 18 Easy setup 17 High throughput Cons 1 HA 1 Long term persistence 1 Get NSQ behavior out of Kafka but not inverse	Pros 3 QoS 2 2 Clusters 1 Plugins
Integrations
No integrations available	Linux Cassandra Kafka MongoDB

What are some alternatives to NSQ, EMQX?

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 gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

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

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.

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

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

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

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

Related Comparisons

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, EMQ provides the following key features:

Full MQTT V3.1/3.1.1 Protocol Specifications Support
Easy to Install - Quick Install on Linux, FreeBSD, Mac and Windows
Massively scalable - Scaling to 1 million connections on a single server

NSQ and EMQ are both open source tools. It seems that NSQ with 16.3K GitHub stars and 2.14K forks on GitHub has more adoption than EMQ with 181 GitHub stars and 96 GitHub forks.

EMQ vs NSQ