Amazon SQS vs NSQ vs Starling

Get Advice Icon

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

Amazon SQS
Amazon SQS

1.2K
618
+ 1
136
NSQ
NSQ

83
114
+ 1
127
Starling
Starling

3
5
+ 1
0
- No public GitHub repository available -

What is 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.

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.

What is Starling?

Starling is a powerful but simple messaging server that enables reliable distributed queuing with an absolutely minimal overhead. It speaks the MemCache protocol for maximum cross-platform compatibility. Any language that speaks MemCache can take advantage of Starling's queue facilities.
Get Advice Icon

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

Why do developers choose Amazon SQS?
Why do developers choose NSQ?
Why do developers choose Starling?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
      What companies use Amazon SQS?
      What companies use NSQ?
      What companies use Starling?

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

      What tools integrate with Amazon SQS?
      What tools integrate with NSQ?
      What tools integrate with Starling?
        No integrations found
          No integrations found

          Sign up to get full access to all the tool integrationsMake informed product decisions

          What are some alternatives to Amazon SQS, NSQ, and Starling?
          Amazon MQ
          Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud.
          Kafka
          Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
          Redis
          Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
          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.
          Amazon SNS
          Amazon Simple Notification Service makes it simple and cost-effective to push to mobile devices such as iPhone, iPad, Android, Kindle Fire, and internet connected smart devices, as well as pushing to other distributed services. Besides pushing cloud notifications directly to mobile devices, SNS can also deliver notifications by SMS text message or email, to Simple Queue Service (SQS) queues, or to any HTTP endpoint.
          See all alternatives
          Decisions about Amazon SQS, NSQ, and Starling
          No stack decisions found
          Interest over time
          Reviews of Amazon SQS, NSQ, and Starling
          No reviews found
          How developers use Amazon SQS, NSQ, and Starling
          Avatar of Karma
          Karma uses Amazon SQSAmazon SQS

          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.

          Avatar of Brandon Adams
          Brandon Adams uses Amazon SQSAmazon SQS

          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.

          Avatar of Simple Merchant
          Simple Merchant uses Amazon SQSAmazon SQS

          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.

          Avatar of InsideSales.com
          InsideSales.com uses NSQNSQ

          The built-in Gamification that comes with our Playbooks application uses NSQ for work queues and microservice communication.

          Avatar of Olo
          Olo uses Amazon SQSAmazon SQS

          Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.

          Avatar of IndiTip
          IndiTip uses Amazon SQSAmazon SQS

          I can't afford to lose data if Dynamo throttles my writes, so everything goes into a message queue first.

          How much does Amazon SQS cost?
          How much does NSQ cost?
          How much does Starling cost?
          Pricing unavailable
          Pricing unavailable
          News about NSQ
          More news