Cost Economics of Amazon SQS and Azure Storage Queue

For any distributed architecture and systems it absolutely incomplete / impossible to build it without a queue. With Cloud driving the computing and architecture to be loosely coupled and queue tie the infrastructures together.

Queue system is indeed very important and both Amazon & Azure have pioneered that during their early entry to the Cloud arena. Amazon came into Amazon Web Services with it first service as SQS – Simple Queue Service in 2004. Actually lot of people think is it S3-Simple Storage Service which is the first offering from AWS, nope it is SQS. During the PDC 2008, Microsoft announced Windows Azure with PaaS infrastructure and Azure Storage Blob, Queue, Table.

Gaurav Mantri has illustrated, well actually investigated about Azure Storage Queue vs Amazon Simple Queue Service. It clearly explain about the various tech specs and capabilities of each of the queues. Here in this post I attempt to explore the cost economics behind it. However in my experience the cost contributing to the overall architecture by the Queues is very less when compared to the compute instances and databases.

Cost Metrics

Azure Storage Queue Amazon Simple Queue Service
In Bandwidth Free Free
Out Bandwidth $0.12 per GB – Up to 10 TB / month, detailed price below $0.120 per GB – Up to 10 TB / month, detailed price below
Storage Cost $0.095 per GB – First 1 TB / Month detailed price below N/A
Transaction Cost $0.01 per 100K Transactions $0.50 per 1000K Transactions (1 Million)

Azure Out Bandwidth details Information

Data Transfer Outbound Zone 1 (US & Europe Data Centers) Zone 2 (Asian Data Centers)
First 10 TB / Month $0.12 per GB $0.19 per GB
Next 40 TB / Month $0.09 per GB $0.15 per GB
Next 100 TB / Month $0.07 per GB  $0.13 per GB
Next 350 TB / Month $0.05 per GB $0.12 per GB
Beyond 350 TB / Month Contact Microsoft Contact Microsoft

Amazon Out Bandwidth details

Storage US East (N. Virginia) US West (Oregon) US West (Northern California) EU (Ireland) Asia Pacific (Singapore) Asia Pacific (Tokyo) Asia Pacific (Sydney) South America (Sao Paulo)
First 1 GB / month $0.000 per GB $0.000 per GB $0.000 per GB $0.000 per GB $0.000 per GB $0.000 per GB $0.000 per GB $0.000 per GB
Up to 10 TB / month $0.120 per GB $0.120 per GB $0.120 per GB $0.120 per GB $0.190 per GB $0.201 per GB $0.120 per GB $0.250 per GB
Next 40 TB / month $0.090 per GB $0.090 per GB $0.090 per GB $0.090 per GB $0.150 per GB $0.158 per GB $0.090 per GB $0.230 per GB
Next 100 TB / month $0.070 per GB $0.070 per GB $0.070 per GB $0.070 per GB $0.130 per GB $0.137 per GB $0.070 per GB $0.210 per GB
Next 350 TB / month $0.050 per GB $0.050 per GB $0.050 per GB $0.050 per GB $0.120 per GB $0.127 per GB $0.050 per GB $0.190 per GB
Next 524 TB / month Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon
Next 4 PB / month Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon
Greater than 5 PB / month Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon Contact Amazon

Cost Information

The above tables illustrated the cost metric during time of posting, the cloud providers Azure and Amazon bring down the pricing at an amazing pace as result of market competition and innovation.

Things Involved in Architecture

Actually the out bandwidth doesn’t count when the queue is consumed or accessed by the components in the same data center i.e. Considering there is a SQS in US East – Virginia data center and if the same SQS queue is accessed by EC2 in the same region, there wont any out band width for the SQS queue but there could out band involved for the EC2 instance when accessed outside. This holds the same for Azure Storage Queue as well.

Importance of Queue Explained by AWS

Closer Watch

Azure charges for the both transaction cost and storage cost for the Queue perhaps it is 64K per queue item plus the meta data associated with the queue. Where as the Amazon just charges for the transaction cost alone. Perhaps this is due to the design of the Azure Storage system itself. Based on the paper Windows Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency, it is just an abstraction layer and  Blob, Queue and Table are handled the same way, my guess is it could be the same reason for the costing and management i.e the costing is same for all the 3 queue, blob, table [Transaction + Storage] and also during the creation we create a storage domain and all the queue, table and blob are handled under the same domain space.

References

  1. http://aws.amazon.com/sqs
  2. http://www.windowsazure.com/en-us/develop/net/how-to-guides/queue-service/
  3. http://www.windowsazure.com/en-us/pricing/calculator/?scenario=full
  4. http://aws.amazon.com/sqs/pricing
  5. http://www.windowsazure.com/en-us/pricing/details
  6. http://sigops.org/sosp/sosp11/current/2011-Cascais/printable/11-calder.pdf
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s