Microsoft, HP to unveil 'solutions built on new infrastructure-to-application model'
Seriously,
Microsoft is once again late to the game.
So, they are attempting to make yet another 'empty' promise for future services that don't exist today.
Microsoft would like nothing better than to have CFOs freeze their Cloud development initiatives and wait for them to catch up.

Image via CrunchBase
Don't limit yourself to a Microsoft-only proprietary Cloud.
AWS is agnostic and gives you flexibility to choose which O/S to use, including Microsoft Windows Server 2008, without any license, if you so choose.
Amazon Web Services is here today.
Mary Jo was kind enough to reply to my Talkback with:
Hi. I agree with you that Microsoft is chasing Amazon in the cloud.
As an Amazon partner, I'm curious whether you agree or have anything to say about a recent blog post claiming Amazon is hitting a scalability wall. Do you think it's true?
Here it is: http://alan.blog-city.com/has_amazon_ec2_become_over_subscribed.htm
MJ
To which I replied:
- There are two sides to a coin, and an edge.
- The
author of the above-referenced article, fails to mention whether they contacted Amazon, and if so, were
AWS technical support able to corroborate any of their issues and/or
what remediation may have taken place in the AWS data center to rectify
their latency issues.

Image via CrunchBase
Also, it should be noted latency, by itself, does not imply a scalability issue.
For example, if a web app user spawned a thread for a 'poorly-optimized' back-end database SQL query, that query might be contributory to latency seen in an app, if the query doesn't return its results in a timely fashion.
Moreover, SQL correlated queries are preferred over nested dynamic queries and if developers of the web app's database were diligent in testing their SQLs (e.g., using Explain) they'd have readily seen where their DB bottlenecks are.
Something as simple as identifying a slow-running query and observing that it is running a 'brute-force' sequential table scan vs indexed read can be remedied with the creation of a new primary key index on the column or columns of the database which are part of a SQL select/insert/delete query statement.
It is stuff like the above that has hit concerns like Twitter. The tools they were using were first suspect (Ruby on Rails), but it was really a matter of their coming to terms with their own programming and scalability issues that ultimately allowed them to become the success they are today. Their scalability issues were not due to the inability of RoR to scale, it was only that they had to go through their own 'learning curve' on how best to configure their servers for peak demand usage that was at issue.
No fault of the tools/resources--just a 'learning experience'. - So,
while I won't rule out the possibility that AWS may have intermittent
'growing pains', I am always concerned when only one side of a story is
given in a blog.
To be fair, the author could have given Amazon the opportunity to provide a response which could have been included in the story.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=d641d530-ae7d-435f-987f-372ecbfbfc8a)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=3d58365e-70f4-4d9a-a4d1-f6e6f106d1b6)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=794315a6-136b-409a-ae73-8a543b9d87fc)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c925cf1e-61a4-4a73-9900-b1eee9ac7d05)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=766169fa-e144-4dae-86a7-13d592d5432b)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=07766ca2-aec6-45b0-a168-f7f9df3297d2)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=27e0dd93-e402-4f16-b027-3cd3e3732f28)


![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c981d848-c06e-462a-a032-6b3cb3d2090a)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=079bbee4-49a7-4f4a-b9bb-d7622d77c79c)


![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=1f3037df-d05f-4872-94ad-d24a150c5aba)

