Need advice about which tool to choose?Ask the StackShare community!
CloudAMQP vs NSQ: What are the differences?
What is CloudAMQP? RabbitMQ as a Service. Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms.
What is 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.
CloudAMQP and NSQ belong to "Message Queue" category of the tech stack.
Some of the features offered by CloudAMQP are:
- Support - 24/7 support, via email, chat and phone.
- Real time metrics and alarms - Get notified in advanced when your queues are growing faster than you're consuming them, when you're servers are over loaded etc. and take action before it becomes a problem.
- Auto-healing - Our monitoring systems automatically detects and fixes a lot of problems such as kernel bugs, auto-restarts, RabbitMQ/Erlang version upgrades etc.
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)
"Some of the best customer support you'll ever find" is the primary reason why developers consider CloudAMQP 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.
Stripe, Docker, and Segment are some of the popular companies that use NSQ, whereas CloudAMQP is used by Travis CI, Guaana, and Apartment List. NSQ has a broader approval, being mentioned in 21 company stacks & 8 developers stacks; compared to CloudAMQP, which is listed in 12 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.
In addition to being a lot cheaper, Google Cloud Pub/Sub allowed us to not worry about maintaining any more infrastructure that needed.
We moved from a self-hosted RabbitMQ over to CloudAMQP and decided that since we use GCP anyway, why not try their managed PubSub?
It is one of the better decisions that we made, and we can just focus about building more important stuff!
Pros of CloudAMQP
- Some of the best customer support you'll ever find4
- Easy to provision3
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 CloudAMQP
Cons of NSQ
- Long term persistence1
- Get NSQ behavior out of Kafka but not inverse1
- HA1