Windows Azure Services Platform

Microsoft intends its new Windows Azure Services Platform to be a serious cloud computing platform for a broad range of developers and scenarios, from lone developers starting up a new Web-based company on a shoestring to large teams of enterprise developers looking for high-performance, highly available, and scalable Web sites, computing, and storage. A few years out, Microsoft wants Azure to be seen as the preferred location for enterprise data, not as a business risk. It's off to a good start.

There's a tremendous amount of capability being presented in the Azure CTP (Community Technology Preview), and there's more to come. It goes beyond simple Web hosting to a flexible architecture designed to automatically enlist additional resources in response to demand. There are capabilities here that I haven't seen in competing cloud offerings -- for example, workflows. The Azure team has picked and chosen existing Microsoft technologies -- virtual servers, the .Net Framework, IIS, worker processes, databases, queues, enterprise service bus, workflows, authentication, and so on -- and adapted them to the cloud.

[ See the Test Center's deep dive into Amazon Web Services, tour of Amazon Elastic Compute Cloud, Google App Engine, AppNexis, and GoGrid, as well as reviews of hosted Web application development environments Coghead and Caspio Bridge. ]

One very promising note is how these services are tied together. The Microsoft of 10 years ago would have created proprietary interfaces to exclude its competitors from taking advantage of its technologies. The Azure team used open standards: REST, SOAP, Atom, and the like. This inclusive choice opens the Azure services to easy integration with almost any programming language and operating system.

Another promising note is how, while breaking new ground, the Azure team made the programming model familiar to developers who have worked with the .Net Framework. You don't have to learn a new programming language or IDE to work with Azure. If you know Visual Studio and C# or Visual Basic .Net, you're good to go, now with relatively little effort. Using other .Net languages and tools is possible but not as well documented. Although using unmanaged code is not yet allowed, it will be in the future.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine