Need advice about which tool to choose?Ask the StackShare community!
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.
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 :)
There are many different messaging frameworks available for IPC use. It's not really a question of how "new" the technology is, but what you need it to do. Azure Service Bus can be a great service to use, but it can also take a lot of effort to administrate and maintain that can make it costly to use unless you need the more advanced features it offers for routing, sequencing, delivery, etc. I would recommend checking out this link to get a basic idea of different messaging architectures. These only cover Azure services, but there are many other solutions that use similar architectural models.
https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services
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.
Mithiridi, I believe you are talking about two different things. 1. If you need to process messages with delays of more 15m or at specific times, it's not a good idea to use queues, independently of tool SQM, Rabbit or Amazon MQ. you should considerer another approach using a scheduled job. 2. For dead queues and policy retries RabbitMQ, for example, doesn't support your use case. https://medium.com/@kiennguyen88/rabbitmq-delay-retry-schedule-with-dead-letter-exchange-31fb25a440fc I'm not sure if that is possible SNS/SQS support, they have a maximum delay for delivery (maxDelayTarget) in seconds but it's not clear the number. You can check this out: https://docs.aws.amazon.com/sns/latest/dg/sns-message-delivery-retries.html
Pros of Amazon SQS
- Easy to use, reliable62
- Low cost40
- Simple28
- Doesn't need to maintain it14
- It is Serverless8
- Has a max message size (currently 256K)4
- Triggers Lambda3
- Easy to configure with Terraform3
- Delayed delivery upto 15 mins only3
- Delayed delivery upto 12 hours3
- JMS compliant1
- Support for retry and dead letter queue1
- D1
Pros of Azure Service Bus
- Easy Integration with .Net4
- Cloud Native2
- Use while high messaging need1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon SQS
- Has a max message size (currently 256K)2
- Proprietary2
- Difficult to configure2
- Has a maximum 15 minutes of delayed messages only1
Cons of Azure Service Bus
- Limited features in Basic tier1
- Skills can only be used in Azure - vendor lock-in1
- Lacking in JMS support1
- Observability of messages in the queue is lacking1
Sign up to add or upvote consMake informed product decisions
What is Amazon SQS?
What is Azure Service Bus?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Azure Service Bus?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Amazon SQS?
What tools integrate with Azure Service Bus?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+47
+30+26
+23+37+25