StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Notifications
  4. Mobile Push Messaging
  5. Amazon SNS vs RabbitMQ

Amazon SNS vs RabbitMQ

OverviewDecisionsComparisonAlternatives

Overview

Amazon SNS
Amazon SNS
Stacks1.4K
Followers1.2K
Votes18
RabbitMQ
RabbitMQ
Stacks21.8K
Followers18.9K
Votes558
GitHub Stars13.2K
Forks4.0K

Amazon SNS vs RabbitMQ: What are the differences?

Amazon SNS is a managed pub/sub messaging service in AWS, while RabbitMQ is an open-source message broker software enabling complex messaging patterns. Let's explore the key differences between them.

  1. Messaging Pattern: SNS follows a publish-subscribe messaging pattern, where messages are published to a topic and then delivered to all subscribed endpoints asynchronously. RabbitMQ follows a queuing pattern, where messages are sent to a queue and then consumed by the consumers when they are ready.

  2. Message Persistence: SNS does not persist messages. Once a message is published, it is not stored for future consumption. RabbitMQ persists messages in queues until they are consumed. This ensures that messages are not lost even if the consumers are not immediately available.

  3. Message Delivery Guarantees: SNS provides at least once delivery guarantee. It ensures that messages are delivered to subscribed endpoints, but there may be duplicates in case of failure or network issues. RabbitMQ provides different delivery guarantees depending on the configuration. It can provide at most once or at least once delivery guarantee based on the acknowledgment settings.

  4. Scaling: SNS can scale up to millions of subscribers and can handle high message throughput. It is designed for massive scale and high availability. RabbitMQ can also handle large message volumes but may require additional configuration and clustering to handle high traffic situations.

  5. Protocol Support: SNS supports multiple protocols such as HTTP, HTTPS, email, SMS, mobile push notifications, and Amazon SQS (Simple Queue Service) as subscribers. RabbitMQ supports various protocols like AMQP (Advanced Message Queuing Protocol), MQTT (Message Queuing Telemetry Transport), and STOMP (Streaming Text Oriented Messaging Protocol).

  6. Managed Service vs Self-Hosted: SNS is a fully managed service provided by AWS. The infrastructure, scaling, and management are handled by AWS, allowing developers to focus on their application logic. RabbitMQ is a self-hosted message broker that requires manual setup, configuration, and maintenance.

In summary, Amazon SNS provides a fully managed solution for message delivery with scalability and ease of setup, whereas RabbitMQ offers more control and customization options for messaging architectures, albeit requiring self-hosting and management.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Amazon SNS, RabbitMQ

viradiya
viradiya

Apr 12, 2020

Needs adviceonAngularJSAngularJSASP.NET CoreASP.NET CoreMSSQLMSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k
Comments
André
André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon.NET Core.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k
Comments
mediafinger
mediafinger

Feb 13, 2019

ReviewonKafkaKafkaRabbitMQRabbitMQ

The question for which Message Queue to use mentioned "availability, distributed, scalability, and monitoring". I don't think that this excludes many options already. I does not sound like you would take advantage of Kafka's strengths (replayability, based on an even sourcing architecture). You could pick one of the AMQP options.

I would recommend the RabbitMQ message broker, which not only implements the AMQP standard 0.9.1 (it can support 1.x or other protocols as well) but has also several very useful extensions built in. It ticks the boxes you mentioned and on top you will get a very flexible system, that allows you to build the architecture, pick the options and trade-offs that suite your case best.

For more information about RabbitMQ, please have a look at the linked markdown I assembled. The second half explains many configuration options. It also contains links to managed hosting and to libraries (though it is missing Python's - which should be Puka, I assume).

159k views159k
Comments

Detailed Comparison

Amazon SNS
Amazon SNS
RabbitMQ
RabbitMQ

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.

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

In most cases, developers can get started with Amazon SNS by using just three APIs: CreateTopic, Subscribe, and Publish. Additional APIs are available, which provide more advanced functionality.;With SNS you can publish a message once, and deliver it one or more times. So you can choose to direct unique messages to individual Apple, Google or Amazon devices, or broadcast deliveries to many mobile devices with a single publish request.;SNS allows you to group multiple recipients using topics. A topic is an “access point” for allowing recipients to dynamically subscribe for identical copies of the same notification. One topic can support deliveries to multiple endpoint types -- for example, you can group together iOS, Android and SMS recipients. When you publish once to a topic, SNS delivers appropriately formatted copies of your message to each subscriber.;Amazon SNS allows applications and end-users on different devices to receive notifications via Mobile Push notification (Apple, Google and Kindle Fire Devices), HTTP/HTTPS, Email/Email-JSON, SMS or Amazon Simple Queue Service (SQS) queues.;Amazon SNS provides access control mechanisms to ensure that topics and messages are secured against unauthorized access
Robust messaging for applications;Easy to use;Runs on all major operating systems;Supports a huge number of developer platforms;Open source and commercially supported
Statistics
GitHub Stars
-
GitHub Stars
13.2K
GitHub Forks
-
GitHub Forks
4.0K
Stacks
1.4K
Stacks
21.8K
Followers
1.2K
Followers
18.9K
Votes
18
Votes
558
Pros & Cons
Pros
  • 12
    Low cost
  • 6
    Supports multi subscribers
Pros
  • 235
    It's fast and it works with good metrics/monitoring
  • 80
    Ease of configuration
  • 60
    I like the admin interface
  • 52
    Easy to set-up and start with
  • 22
    Durable
Cons
  • 9
    Too complicated cluster/HA config and management
  • 6
    Needs Erlang runtime. Need ops good with Erlang runtime
  • 5
    Configuration must be done first, not by your code
  • 4
    Slow

What are some alternatives to Amazon SNS, RabbitMQ?

Kafka

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

Celery

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

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.

NSQ

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.

OneSignal

OneSignal

OneSignal is a high volume push notification service for websites and mobile applications. OneSignal supports all major native and mobile platforms by providing dedicated SDKs for each platform, a RESTful server API, and a dashboard.

ActiveMQ

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

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

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

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

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.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase