Alin Irimie's Azure Blog

After more than two “azure” months, with lots of new stuff to learn, a whole new alphabet soup to digest and a dozen or so Microsoft evangelists trying to navigate us through the plethora of “cloud services” that seem to pop up every day from Microsoft’s software-making machine, I believe something is not right with with the way the information is presented to the public or with the overall Microsoft strategy. Let me explain.

First of all, everybody is using nowadays “cloud” to describe anything that runs on the web. Cloud is the new buzzword, and Microsoft jumping on the bandwagon doesn’t make things any better. Before Windows Azure release, it was simple to explain “the cloud” to any CEO - we had Amazon with storage and computing power, we had Google with their app engine and some other smaller “cloud computing” offerings. Everything else was SaaS - Software as a Service. After Windows Azure release, looks like everything Microsoft releases is a “cloud service” - Exchange, Sharepoint, Office, Live Services etc. - just adding to the confusion about what “cloud computing” actually is. I believe Microsoft should have come up with a different buzzword to describe their Software as a Service/Software + Services offerings, one word, not many.

Second, Microsoft should clarify better whether Windows Azure platform is a .NET platform or a “mixed” platform where legacy application can run. Also, when they advertise “Windows Azure is an open platform that will support both Microsoft and non-Microsoft languages and environments“, they should explain better what exactly it means - can I write Erlang code, deploy and run it in the “cloud” or it means that I can access the services from outside the azure cloud? Every time I’m asked to recommend a “cloud” solution for a software application, I struggle with finding the answers to basic questions. Before scalability, reliability, and security, there are more basic questions that need to be answered and Microsoft doesn’t make it any easier. See, it is much easier to pitch an Amazon solution and easier for a CIO/CEO to understand.

Third, Microsoft needs to let us know at least the year Windows Azure will be released. When are we going to have an SLA. Also, please update the case studies on the windows azure website, because believe it or not, people look at them. It will be interesting to see the evolution of the showcased services, because without any updates they are just proof of concepts, evangelism material Microsoft created. And most important thing is - let us know which Microsoft products are using Windows Azure as a platform and how is it used - because unless Microsoft is using their own services, I cannot recommend the platform to anybody (lessons learned from .NET 1.1 release).

As I said, I have a bad feeling about Windows Azure. I’m not sure what it is but there’s something missing, something is not going right with it. Hopefully this new year will bring us some clarity in the clouds.

• Are Humans Really Necessary for Maintaining SLAs in the Cloud?
• The Importance of Cloud Abstraction
• Microsoft Should Release Windows Azure This Year
• SLA for Microsoft Azure, When? -Microsoft's Response
• Microsoft's Ray Ozzie Thinks It's Still Early Days for Cloud Computing