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

Mosquitto

95
203
+ 1
12
NSQ

118
269
+ 1
143
Add tool

Mosquitto vs NSQ: What are the differences?

Developers describe Mosquitto as "An open source message broker that implements the MQTT protocol". It is lightweight and is suitable for use on all devices from low power single board computers to full servers.. The MQTT protocol provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for Internet of Things messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers. On the other hand, NSQ is detailed 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.

Mosquitto and NSQ can be primarily classified as "Message Queue" tools.

NSQ is an open source tool with 15.6K GitHub stars and 2.03K GitHub forks. Here's a link to NSQ's open source repository on GitHub.

Stripe, Docker, and Segment are some of the popular companies that use NSQ, whereas Mosquitto is used by Teleolabs, Xanview Ltd, and Future Corporation. NSQ has a broader approval, being mentioned in 21 company stacks & 8 developers stacks; compared to Mosquitto, which is listed in 3 company stacks and 3 developer stacks.

Advice on Mosquitto and NSQ
Pramod Nikam
Co Founder at Usability Designs · | 2 upvotes · 184.1K views
Needs advice
on
NSQ
Kafka
and
Apache Thrift

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 · 181.4K views
Recommends
Kafka

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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Mosquitto
Pros of NSQ
  • 8
    Simple and light
  • 4
    Performance
  • 29
    It's in golang
  • 20
    Lightweight
  • 19
    Distributed
  • 18
    Easy setup
  • 16
    High throughput
  • 10
    Publish-Subscribe
  • 7
    Save data if no subscribers are found
  • 7
    Scalable
  • 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

Sign up to add or upvote prosMake informed product decisions

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

    Sign up to add or upvote consMake informed product decisions

    What is Mosquitto?

    It is lightweight and is suitable for use on all devices from low power single board computers to full servers.. The MQTT protocol provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for Internet of Things messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers.

    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.

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

    What companies use Mosquitto?
    What companies use NSQ?
    See which teams inside your own company are using Mosquitto or NSQ.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Mosquitto?
    What tools integrate with NSQ?
      No integrations found
      What are some alternatives to Mosquitto and NSQ?
      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.
      Mosca
      A Node.js MQTT broker, which can be used as a Standalone Service or embedded in another Node.js application.
      EMQ
      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.
      VerneMQ
      VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP. It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications.
      RabbitMQ
      RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
      See all alternatives