Amazon SQS vs EMQ

Overview

Amazon SQS

Stacks2.8K

Followers2.0K

Votes171

EMQX

Stacks34

Followers109

Votes6

GitHub Stars15.4K

Forks2.4K

Amazon SQS vs EMQ: What are the differences?

Introduction

Amazon Simple Queue Service (SQS) and EMQ are both messaging systems provided by Amazon Web Services (AWS) for building distributed applications. While they serve a similar purpose of enabling message-based communication between components, there are several key differences between them.

Scaling and Capacity: One key difference between Amazon SQS and EMQ lies in their scaling and capacity capabilities. Amazon SQS is a fully managed service that automatically scales to accommodate the message volume and throughput needed by applications. It supports an unlimited number of messages and provides high message availability. On the other hand, EMQ is an open-source MQTT broker that allows users to deploy and manage their own messaging infrastructure. Scaling and capacity management in EMQ require manual configuration and optimization.
Message Delivery Guarantees: Another important difference between Amazon SQS and EMQ is their approach to message delivery guarantees. Amazon SQS offers a "At Least Once" delivery guarantee, which ensures that messages are not lost but may be delivered multiple times. It achieves this by storing messages redundantly across multiple data centers. In contrast, EMQ guarantees "at most once" message delivery, where messages may be lost if delivering to a subscriber fails or if the subscriber disconnects. This approach allows for lower overhead and latency but introduces the possibility of message loss.
Message Filtering: Amazon SQS provides a feature called "message filtering" that allows subscribers to specify criteria for receiving only a subset of messages from a queue. This feature enables more fine-grained control over message processing and reduces the amount of data transferred. EMQ, as an MQTT broker, does not have built-in message filtering capabilities. Filtering in EMQ usually requires an additional layer of processing or an external component.
Pricing Model: The pricing model of Amazon SQS and EMQ also differs. Amazon SQS charges based on the number of requests made (sending, receiving, and deleting messages) as well as the amount of data transferred. In contrast, EMQ, being an open-source software, is free to use and does not have any direct costs. However, users need to consider the costs associated with running and maintaining their own infrastructure.
Protocol Support: Amazon SQS supports multiple protocols for sending and receiving messages, including HTTP, HTTPS, and Amazon SDKs for various programming languages. It ensures seamless integration with different types of applications and systems. EMQ, being an MQTT broker, primarily supports the MQTT (Message Queuing Telemetry Transport) protocol, which is a lightweight publish-subscribe messaging protocol designed for constrained devices and low-bandwidth networks. This makes EMQ a better choice for IoT applications and scenarios where the MQTT protocol is preferred.
Management and Monitoring: Amazon SQS provides a comprehensive set of management tools and monitoring capabilities through AWS Management Console, SDKs, and APIs. It allows users to easily configure and monitor their queues, set up alarms, and track performance metrics. EMQ, being a self-managed messaging broker, relies on external monitoring and management tools. Users need to employ third-party solutions or develop their own monitoring and management systems.

In summary, Amazon SQS is a fully managed messaging service with automatic scaling and high message availability, offering "At Least Once" delivery guarantee, message filtering, and comprehensive management tools. EMQ, an open-source MQTT broker, requires manual scaling and capacity management, provides "at most once" delivery guarantee, lacks built-in message filtering, has no direct costs but requires users to manage their own infrastructure, supports the MQTT protocol primarily, and relies on external monitoring and management tools.

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)

Manual

Advice on Amazon SQS, EMQX

MITHIRIDI

Software Engineer at LightMetrics

May 8, 2020

Needs adviceon

Amazon SQS

Amazon MQ

I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.

Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.

303k views303k

Comments

Detailed Comparison

Amazon SQS	EMQX
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.	EMQX is a cloud-native, MQTT-based, IoT messaging platform designed for high reliability and massive scale. Licensed under the Apache Version 2.0, EMQX is 100% compliant with MQTT 5.0 and 3.x standard protocol specifications.
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.	Scale to 100 million concurrent MQTT connections with a single EMQX 5.0 cluster./Licensed under the Apache Version 2.0, 100% compliant with MQTT 5.0 and 3.x standard protocol specifications for better scalability, security, and reliability./Move and process millions of MQTT messages per second in a single broker./Guarantee sub-millisecond latency in message delivery with the soft real-time runtime./Achieve high availability and horizontal scalability with a masterless distributed architecture./Easy to deploy on-premises and in public clouds with Kubernetes Operator and Terraform.
Statistics
GitHub Stars -	GitHub Stars 15.4K
GitHub Forks -	GitHub Forks 2.4K
Stacks 2.8K	Stacks 34
Followers 2.0K	Followers 109
Votes 171	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 Has a max message size (currently 256K) 2 Difficult to configure 2 Proprietary 1 Has a maximum 15 minutes of delayed messages only	Pros 3 QoS 2 2 Clusters 1 Plugins
Integrations
No integrations available	Linux Cassandra Kafka MongoDB

What are some alternatives to Amazon SQS, EMQX?

Kafka

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

RabbitMQ

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

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.

Related Comparisons

Amazon SQS vs EMQ: What are the differences?

Introduction

Scaling and Capacity: One key difference between Amazon SQS and EMQ lies in their scaling and capacity capabilities. Amazon SQS is a fully managed service that automatically scales to accommodate the message volume and throughput needed by applications. It supports an unlimited number of messages and provides high message availability. On the other hand, EMQ is an open-source MQTT broker that allows users to deploy and manage their own messaging infrastructure. Scaling and capacity management in EMQ require manual configuration and optimization.
Message Delivery Guarantees: Another important difference between Amazon SQS and EMQ is their approach to message delivery guarantees. Amazon SQS offers a "At Least Once" delivery guarantee, which ensures that messages are not lost but may be delivered multiple times. It achieves this by storing messages redundantly across multiple data centers. In contrast, EMQ guarantees "at most once" message delivery, where messages may be lost if delivering to a subscriber fails or if the subscriber disconnects. This approach allows for lower overhead and latency but introduces the possibility of message loss.
Message Filtering: Amazon SQS provides a feature called "message filtering" that allows subscribers to specify criteria for receiving only a subset of messages from a queue. This feature enables more fine-grained control over message processing and reduces the amount of data transferred. EMQ, as an MQTT broker, does not have built-in message filtering capabilities. Filtering in EMQ usually requires an additional layer of processing or an external component.
Pricing Model: The pricing model of Amazon SQS and EMQ also differs. Amazon SQS charges based on the number of requests made (sending, receiving, and deleting messages) as well as the amount of data transferred. In contrast, EMQ, being an open-source software, is free to use and does not have any direct costs. However, users need to consider the costs associated with running and maintaining their own infrastructure.
Protocol Support: Amazon SQS supports multiple protocols for sending and receiving messages, including HTTP, HTTPS, and Amazon SDKs for various programming languages. It ensures seamless integration with different types of applications and systems. EMQ, being an MQTT broker, primarily supports the MQTT (Message Queuing Telemetry Transport) protocol, which is a lightweight publish-subscribe messaging protocol designed for constrained devices and low-bandwidth networks. This makes EMQ a better choice for IoT applications and scenarios where the MQTT protocol is preferred.
Management and Monitoring: Amazon SQS provides a comprehensive set of management tools and monitoring capabilities through AWS Management Console, SDKs, and APIs. It allows users to easily configure and monitor their queues, set up alarms, and track performance metrics. EMQ, being a self-managed messaging broker, relies on external monitoring and management tools. Users need to employ third-party solutions or develop their own monitoring and management systems.

Amazon SQS vs EMQ

Overview