Need advice about which tool to choose?Ask the StackShare community!
IronMQ vs NSQ: What are the differences?
IronMQ: Message Queue for any deployment. 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; 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.
IronMQ and NSQ belong to "Message Queue" category of the tech stack.
Some of the features offered by IronMQ are:
- Instant High Availability- Runs on top cloud infrastructures and uses multiple high-availability data centers. Uses reliable datastores for message durability and persistence.
- Easy to Use- IronMQ is super easy to use. Simply connect directly to the API endpoints and you're ready to create and use queues. There are also client libraries available in any language you want – Ruby, Python, PHP, Java, .NET, Go, Node.JS, and more
- Scalable / High Performance- Built using high-performance languages designed for concurrency and runs on industrial-strength clouds. Push messages and stream data at will without worrying about memory limits or adding more servers.
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)
"Great Support" is the primary reason why developers consider IronMQ over the competitors, whereas "It's in golang" was stated as the key factor in picking NSQ.
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.
According to the StackShare community, NSQ has a broader approval, being mentioned in 21 company stacks & 8 developers stacks; compared to IronMQ, which is listed in 9 company stacks and 5 developer stacks.
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 IronMQ
- Great Support12
- Heroku Add-on8
- Push support3
- Delayed delivery upto 7 days3
- Super fast2
- Language agnostic2
- Good analytics/monitoring2
- Ease of configuration2
- GDPR Compliant2
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 IronMQ
- Can't use rabbitmqadmin1
Cons of NSQ
- Long term persistence1
- Get NSQ behavior out of Kafka but not inverse1
- HA1
