IronMQ vs NSQ

Overview

IronMQ

Stacks35

Followers49

Votes36

NSQ

Stacks141

Followers356

Votes148

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.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

0

1

Advice on IronMQ, NSQ

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

IronMQ	NSQ
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 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.
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.;Realtime Monitoring- Get realtime monitoring of your message queues through IronMQ's beautiful dashboard. This allows you to quickly find, diagnose, and resolve problems before others notice.;One-time FIFO delivery;Push Queues and publish-subscribe support;Queue messages using webhooks	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)
Statistics
Stacks 35	Stacks 141
Followers 49	Followers 356
Votes 36	Votes 148
Pros & Cons
Pros 12 Great Support 8 Heroku Add-on 3 Delayed delivery upto 7 days 3 Push support 2 GDPR Compliant Cons 1 Can't use rabbitmqadmin	Pros 29 It's in golang 20 Distributed 20 Lightweight 18 Easy setup 17 High throughput Cons 1 Long term persistence 1 HA 1 Get NSQ behavior out of Kafka but not inverse
Integrations
Amazon EC2 Heroku Engine Yard Cloud Rackspace Cloud Servers Red Hat OpenShift StackMob AppFog cloudControl	No integrations available

What are some alternatives to IronMQ, NSQ?

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.

Apache Pulsar

Apache Pulsar is a distributed messaging solution developed and released to open source at Yahoo. Pulsar supports both pub-sub messaging and queuing in a platform designed for performance, scalability, and ease of development and operation.