Need advice about which tool to choose?Ask the StackShare community!
Mosca vs NSQ: What are the differences?
Mosca: A Node.js MQTT broker. A Node.js MQTT broker, which can be used as a Standalone Service or embedded in another Node.js application; 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.
Mosca and NSQ belong to "Message Queue" category of the tech stack.
Some of the features offered by Mosca are:
- MQTT 3.1 and 3.1.1 compliant
- QoS 0 and QoS 1
- Various storage options for QoS 1 offline packets, and subscriptions
On the other hand, NSQ provides the following key features:
- support distributed topologies with no SPOF
- horizontally scalable (no brokers, seamlessly add more nodes to the cluster)
- low-latency push based message delivery (performance)
Mosca and NSQ are both open source tools. It seems that NSQ with 15.6K GitHub stars and 2.03K forks on GitHub has more adoption than Mosca with 2.84K GitHub stars and 501 GitHub forks.
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.
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.
Pros of Mosca
Pros of NSQ
- It's in golang29
- Distributed20
- Lightweight20
- Easy setup18
- High throughput17
- Publish-Subscribe11
- Scalable8
- Save data if no subscribers are found8
- Open source6
- Temporarily kept on disk5
- Simple-to use2
- Free1
- Topics and channels concept1
- Load balanced1
- Primarily in-memory1
Sign up to add or upvote prosMake informed product decisions
Cons of Mosca
Cons of NSQ
- Long term persistence1
- Get NSQ behavior out of Kafka but not inverse1
- HA1