Amazon SQS vs NSQ: What are the differences?
What is Amazon SQS? Fully managed message queuing service. 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.
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.
Amazon SQS and NSQ can be primarily classified as "Message Queue" tools.
Some of the features offered by Amazon SQS are:
- A queue can be created in any region.
- The message payload can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.
- Messages can be sent, received or deleted in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.
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)
"Easy to use, reliable" is the top reason why over 45 developers like Amazon SQS, while over 23 developers mention "It's in golang" as the leading cause for choosing NSQ.
NSQ is an open source tool with 15.5K GitHub stars and 2.04K GitHub forks. Here's a link to NSQ's open source repository on GitHub.
Lyft, SendGrid, and PedidosYa are some of the popular companies that use Amazon SQS, whereas NSQ is used by Stripe, Movable Ink, and Path. Amazon SQS has a broader approval, being mentioned in 381 company stacks & 101 developers stacks; compared to NSQ, which is listed in 21 company stacks and 8 developer stacks.
What is Amazon SQS?
What is NSQ?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with NSQ?
Sign up to get full access to all the tool integrationsMake informed product decisions
In the beginning we thought we wanted to start using something like RabbitMQ or maybe Kafka or maybe ActiveMQ. Back then we only had a few developers and no ops people. That has changed now, but we didn't really look forward to setting up a queuing cluster and making sure that all works.
What we did instead was we looked at what services Amazon offers to see if we can use those to build our own messaging system within those services. That's basically what we did. We wrote some clients in Ruby that can basically do the entire orchestration for us, and we run all our messaging on both SNS and SQS. Basically what you can do in Amazon services is you can use Amazon Simple Notification Service, so SNS, for creating topics and you can use queues to subscribe to these topics. That's basically all you need for a messaging system. You don't have to worry about scalability at all. That's what really appealed to us.
This isn't exactly low-latency (10s to 100s of milliseconds), but it has good throughput and a simple API. There is good reliability, and there is no configuration necessary to get up and running. A hosted queue is important when trying to move fast.
SQS is the bridge between our new Lambda services and our incumbent Rails applications. Extremely easy to use when you're already using other AWS infrastructure.
The built-in Gamification that comes with our Playbooks application uses NSQ for work queues and microservice communication.
Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.