Overview

Amazon SQS

Stacks2.3K

Followers2.0K

Votes171

RabbitMQ

Stacks21.7K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

RSMQ

Stacks4

Followers87

Votes6

GitHub Stars1.8K

Forks120

Amazon SQS vs RSMQ vs RabbitMQ: What are the differences?

Introduction

In the world of message brokers, three popular options are Amazon Simple Queue Service (SQS), Redis Simple Message Queue (RSMQ), and RabbitMQ. While all three serve a similar purpose of managing message queues, there are key differences that set them apart. This article will outline six of these differences.

Architecture: Amazon SQS is a fully managed message queuing service provided by AWS. It offers a highly scalable, distributed architecture where messages are stored redundantly across multiple Availability Zones. RSMQ and RabbitMQ, on the other hand, are self-hosted message brokers. RSMQ relies on a single Redis server, while RabbitMQ uses a distributed cluster architecture.
Protocol Support: Amazon SQS offers an HTTP/HTTPS-based API for interacting with the message queues. It supports both short and long polling to efficiently retrieve messages. RSMQ also provides an HTTP-based REST API, but it operates over Redis directly. RabbitMQ, however, supports multiple protocols including AMQP, MQTT, and STOMP, making it more versatile in terms of integration possibilities.
Message Ordering: Amazon SQS guarantees that messages will be delivered in the order they were sent, although delays can occur. RSMQ, on the other hand, does not guarantee message ordering. It assigns a message ID to each message and retrieves them based on priority and timestamp. RabbitMQ offers various message ordering guarantees, including message publication order within a single channel and the use of ordered queues for strict ordering.
Message Retention: Amazon SQS retains messages in the queue for up to 14 days, ensuring durability even in case of system failures. RSMQ allows setting a retention time for individual messages, but it does not provide built-in persistence options. RabbitMQ persists messages on disk by default and allows configuring different retention policies based on message age or queue size.
Scalability: Amazon SQS automatically scales horizontally to handle increasing message volumes and supports batch operations for improved efficiency. RSMQ's scalability is limited by the capacity of the Redis server it relies upon. RabbitMQ is also highly scalable, with the ability to distribute messages across a cluster of nodes for increased throughput and fault tolerance.
Managed Service vs. Self-hosted: Amazon SQS is a fully managed service, which means that AWS takes care of all the infrastructure and maintenance tasks. RSMQ and RabbitMQ require setting up and managing the message broker infrastructure yourself, offering more control but also more responsibilities.

In Summary, while all three options provide message queuing capabilities, Amazon SQS is a fully managed, highly scalable service offered by AWS. RSMQ relies on a single Redis server and offers an HTTP-based API, while RabbitMQ is a self-hosted message broker supporting multiple protocols and offering advanced features like strict message ordering and flexible retention policies.

Advice on Amazon SQS, RabbitMQ, RSMQ

viradiya

Apr 12, 2020

Needs adviceon

AngularJS

ASP.NET Core

MSSQL

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

Kirill

GO/C developer at Duckling Sales

Feb 16, 2021

Decided

Maybe not an obvious comparison with Kafka, since Kafka is pretty different from rabbitmq. But for small service, Rabbit as a pubsub platform is super easy to use and pretty powerful. Kafka as an alternative was the original choice, but its really a kind of overkill for a small-medium service. Especially if you are not planning to use k8s, since pure docker deployment can be a pain because of networking setup. Google PubSub was another alternative, its actually pretty cheap, but I never tested it since Rabbit was matching really good for mailing/notification services.

266k views266k

Comments

André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon

.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

Detailed Comparison

Amazon SQS	RabbitMQ	RSMQ
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.	RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	tl;dr: If you run a Redis server and currently use Amazon SQS or a similar message queue you might as well use this fast little replacement. Using a shared Redis server multiple Node.js processes can send / receive messages.
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.;Long polling reduces extraneous polling to help you minimize cost while receiving new messages as quickly as possible. When your queue is empty, long-poll requests wait up to 20 seconds for the next message to arrive. Long poll requests cost the same amount as regular requests.;Messages can be retained in queues for up to 14 days.;Messages can be sent and read simultaneously.;Developers can get started with Amazon SQS by using only five APIs: CreateQueue, SendMessage, ReceiveMessage, ChangeMessageVisibility, and DeleteMessage. Additional APIs are available to provide advanced functionality.	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	Lightweight: Just Redis and ~500 lines of javascript.;Guaranteed delivery of a message to exactly one recipient within a messages visibility timeout.;Received messages that are not deleted will reappear after the visibility timeout.;Test coverage;Optional RESTful interface via rest-rsmq
Statistics
GitHub Stars -	GitHub Stars 13.2K	GitHub Stars 1.8K
GitHub Forks -	GitHub Forks 4.0K	GitHub Forks 120
Stacks 2.3K	Stacks 21.7K	Stacks 4
Followers 2.0K	Followers 18.9K	Followers 87
Votes 171	Votes 558	Votes 6
Pros & Cons
Pros 62 Easy to use, reliable 40 Low cost 28 Simple 14 Doesn't need to maintain it 8 It is Serverless Cons 2 Proprietary 2 Has a max message size (currently 256K) 2 Difficult to configure 1 Has a maximum 15 minutes of delayed messages only	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	Pros 2 Simple, does one thing well 1 Written in TypeScript 1 Written in Coffeescript 1 Backed by Redis 1 Comes with a visibility timeout feature similar to AWS
Integrations
No integrations available	No integrations available	Redis

What are some alternatives to Amazon SQS, RabbitMQ, RSMQ?

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 is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

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.

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.

IronMQ

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.

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.