Amazon SQS vs Azure Service Bus

Overview

Amazon SQS

Stacks2.8K

Followers2.0K

Votes171

Azure Service Bus

Stacks553

Followers536

Votes7

Amazon SQS vs Azure Service Bus: What are the differences?

Message Ordering and Delivery Guarantees:
- Amazon SQS: Amazon SQS doesn't provide explicit guarantees for the order in which messages are received or delivered. However, messages can be sent with a sequence number to enforce ordering, but it's not inherently guaranteed.
- Azure Service Bus: Azure Service Bus supports both FIFO (First-In-First-Out) and publish-subscribe message ordering. It ensures that messages are delivered in the same order they were sent.
Message Size Limitations:
- Amazon SQS: Amazon SQS has a maximum message size limitation of 256 KB for standard queues and 2 GB for large payload queues.
- Azure Service Bus: Azure Service Bus has a message size limit of 256 KB for standard, partitioned, and dead-lettered queues.
Integrations and Protocols Supported:
- Amazon SQS: Amazon SQS supports HTTP/HTTPS, AWS SDKs, and RESTful APIs for integration purposes.
- Azure Service Bus: Azure Service Bus offers support for messaging protocols like AMQP, HTTPS, and advanced integration capabilities with Azure Functions, Logic Apps, and Event Grid.
Dead-Lettering and Retry Mechanisms:
- Amazon SQS: Amazon SQS provides a dead-letter queue where messages can be automatically moved after a defined number of unsuccessful retries. It allows developers to investigate and handle problematic messages.
- Azure Service Bus: Azure Service Bus also supports dead-lettering of messages, but it provides more advanced retry mechanisms such as exponential backoff and automatic retries with polices for message handling.
Pricing and Cost Structure:
- Amazon SQS: Amazon SQS offers a pay-as-you-go pricing model based on the number of requests and data transfer rates.
- Azure Service Bus: Azure Service Bus follows a similar pay-as-you-go pricing model, but with additional pricing tiers based on different performance and usage needs.
Supported Messaging Patterns:
- Amazon SQS: Amazon SQS mainly supports point-to-point messaging patterns, making it suitable for decoupling components in distributed systems.
- Azure Service Bus: Azure Service Bus supports multiple messaging patterns, including point-to-point, publish-subscribe, and request-response, providing flexibility for different messaging scenarios.

In Summary, Amazon SQS and Azure Service Bus differ in terms of message ordering guarantees, message size limitations, supported integrations, dead-lettering and retry mechanisms, pricing and cost structure, as well as supported messaging patterns. These differences make them suitable for various use cases depending on specific requirements.

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, Azure Service Bus

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

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	Azure Service Bus
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.	It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline.
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.	-
Statistics
Stacks 2.8K	Stacks 553
Followers 2.0K	Followers 536
Votes 171	Votes 7
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 4 Easy Integration with .Net 2 Cloud Native 1 Use while high messaging need Cons 1 Limited features in Basic tier 1 Skills can only be used in Azure - vendor lock-in 1 Observability of messages in the queue is lacking 1 Lacking in JMS support

What are some alternatives to Amazon SQS, Azure Service Bus?

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 Azure Service Bus: What are the differences?

Message Ordering and Delivery Guarantees:
- Amazon SQS: Amazon SQS doesn't provide explicit guarantees for the order in which messages are received or delivered. However, messages can be sent with a sequence number to enforce ordering, but it's not inherently guaranteed.
- Azure Service Bus: Azure Service Bus supports both FIFO (First-In-First-Out) and publish-subscribe message ordering. It ensures that messages are delivered in the same order they were sent.
Message Size Limitations:
- Amazon SQS: Amazon SQS has a maximum message size limitation of 256 KB for standard queues and 2 GB for large payload queues.
- Azure Service Bus: Azure Service Bus has a message size limit of 256 KB for standard, partitioned, and dead-lettered queues.
Integrations and Protocols Supported:
- Amazon SQS: Amazon SQS supports HTTP/HTTPS, AWS SDKs, and RESTful APIs for integration purposes.
- Azure Service Bus: Azure Service Bus offers support for messaging protocols like AMQP, HTTPS, and advanced integration capabilities with Azure Functions, Logic Apps, and Event Grid.
Dead-Lettering and Retry Mechanisms:
- Amazon SQS: Amazon SQS provides a dead-letter queue where messages can be automatically moved after a defined number of unsuccessful retries. It allows developers to investigate and handle problematic messages.
- Azure Service Bus: Azure Service Bus also supports dead-lettering of messages, but it provides more advanced retry mechanisms such as exponential backoff and automatic retries with polices for message handling.
Pricing and Cost Structure:
- Amazon SQS: Amazon SQS offers a pay-as-you-go pricing model based on the number of requests and data transfer rates.
- Azure Service Bus: Azure Service Bus follows a similar pay-as-you-go pricing model, but with additional pricing tiers based on different performance and usage needs.
Supported Messaging Patterns:
- Amazon SQS: Amazon SQS mainly supports point-to-point messaging patterns, making it suitable for decoupling components in distributed systems.
- Azure Service Bus: Azure Service Bus supports multiple messaging patterns, including point-to-point, publish-subscribe, and request-response, providing flexibility for different messaging scenarios.

Amazon SQS vs Azure Service Bus

Overview