Amazon SQS vs Mosca: 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; Mosca: A Node.js MQTT broker. A Node.js MQTT broker, which can be used as a Standalone Service or embedded in another Node.js application.

Amazon SQS and Mosca 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, Mosca provides the following key features:

• MQTT 3.1 and 3.1.1 compliant
• QoS 0 and QoS 1
• Various storage options for QoS 1 offline packets, and subscriptions

Mosca is an open source tool with 2.84K GitHub stars and 501 GitHub forks. Here's a link to Mosca's open source repository on GitHub.