Amazon SQS vs RSMQ

Amazon SQS vs RSMQ: What are the differences?

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; RSMQ: A lightweight message queue for Node.js that requires no dedicated queue server. Just a Redis server. 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.

Amazon SQS and RSMQ can be categorized 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, RSMQ provides the following key features:

• 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.

RSMQ is an open source tool with 1.07K GitHub stars and 78 GitHub forks. Here's a link to RSMQ's open source repository on GitHub.