Amazon SQS vs Azure Storage: 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; Azure Storage: Reliable, economical cloud storage for data big and small. Azure Storage provides the flexibility to store and retrieve large amounts of unstructured data, such as documents and media files with Azure Blobs; structured nosql based data with Azure Tables; reliable messages with Azure Queues, and use SMB based Azure Files for migrating on-premises applications to the cloud.
Amazon SQS belongs to "Message Queue" category of the tech stack, while Azure Storage can be primarily classified under "Cloud Storage".
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, Azure Storage provides the following key features:
- Blobs, Tables, Queues, and Files
- Highly scalable
- Durable & highly available
"Easy to use, reliable" is the top reason why over 45 developers like Amazon SQS, while over 18 developers mention "All-in-one storage solution" as the leading cause for choosing Azure Storage.
Medium, Lyft, and Coursera are some of the popular companies that use Amazon SQS, whereas Azure Storage is used by Microsoft, Starbucks, and Yammer. Amazon SQS has a broader approval, being mentioned in 384 company stacks & 103 developers stacks; compared to Azure Storage, which is listed in 84 company stacks and 44 developer stacks.
What is Amazon SQS?
What is Azure Storage?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Azure Storage?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
In the beginning we thought we wanted to start using something like RabbitMQ or maybe Kafka or maybe ActiveMQ. Back then we only had a few developers and no ops people. That has changed now, but we didn't really look forward to setting up a queuing cluster and making sure that all works.
What we did instead was we looked at what services Amazon offers to see if we can use those to build our own messaging system within those services. That's basically what we did. We wrote some clients in Ruby that can basically do the entire orchestration for us, and we run all our messaging on both SNS and SQS. Basically what you can do in Amazon services is you can use Amazon Simple Notification Service, so SNS, for creating topics and you can use queues to subscribe to these topics. That's basically all you need for a messaging system. You don't have to worry about scalability at all. That's what really appealed to us.
This isn't exactly low-latency (10s to 100s of milliseconds), but it has good throughput and a simple API. There is good reliability, and there is no configuration necessary to get up and running. A hosted queue is important when trying to move fast.
SQS is the bridge between our new Lambda services and our incumbent Rails applications. Extremely easy to use when you're already using other AWS infrastructure.
We use Azure Blob Storage for hosting all images on the Seen on Set website. These images are then geo-cached using Azure CDN.
We use Azure Storage to store all foundbite images and sound. Azure Storage is super easy to use and really cheap.
Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.
Azure Storage is used as a scalable NoSQL storage to prevent bottlenecks when the amount of data is growing.
I can't afford to lose data if Dynamo throttles my writes, so everything goes into a message queue first.