The Windows Azure Architect’s Reference

My degree was not in computer science, I’m a mechanical engineer in disguise. On the first week of my degree course I was given a reference book which contained all kinds of useful facts, figures and formulas which you can pull together to construct a mathematical model of the world (which is what half of engineering is about). This book had everything from the periodic table, to the formulas for Newtonian physics, the tensile strength of various steels to the formulas for fluid mechanics. It was really useful.

In the IT world we face similar problems. We construct a solution to a problem by pulling together various technologies. However, we often rely on gut instinct (or experience) to know whether a solution will scale in an acceptable way (I’m guilty of this sometimes anyway).

Rob Blackwell suggested that we pull together a one page summary on the features in Windows Azure, to provide architects with a reference to help inform design decisions. This doesn’t include cost information, as this is well served by the calculator, but it does include performance expectations, SLAs, and naming restrictions. All figures come straight from MSDN documentation, so there’s no original content here, just a collation of data already on the internet:

There are a large number of gaps at the moment, and perhaps you can help to fill them in? I hope this is something that will grow over time, and become increasingly useful.