Windows Azure limits – a reminder that they exist


Whist reading through Architecture of Tankster– Scale (Part 2) I noted that Nathan had looked at some of the performance and size limitations of the Windows Azure Platform and how they would impact the architecture of the solution. I have previously pointed at this post by the team from May 2010 which digs into Azure Storage in detail and includes details on limits etc.

In Nathans case he needed to work within the following:

A single Windows Azure storage account has the following scalability targets:

  • Storage Capacity: Up to 100 TBs
  • Transactions: Up to 5,000 entities/messages/blobs per second
  • Bandwidth: Up to 3 gigabits per second

A single Windows Azure queue:

  • Bandwidth: Up to 500 messages per second

A single blob:

  • Bandwidth: Up to 60 megabytes per second.

Related Links:

Advertisements

2 thoughts on “Windows Azure limits – a reminder that they exist

  1. Pingback: Windows Azure limits – a reminder that they exist - IUpdateable from Eric Nelson (https://ericnelson.wordpress.com) - Site Home - MSDN Blogs

  2. Pingback: Automating Azure 1.4 Packaging using MSBuild and CSPack–via Iain Hunter | IUpdateable from Eric Nelson (UK)

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