Desmond File

Blog archive

PDC: Windows Azure Goes Live

As expected, Microsoft rolled out its cloud computing vision during the opening keynote of PDC 2008 this morning, and I have to say, there were surprisingly few, um, surprises.

Don't get me wrong -- the services-based cloud operating system known formerly as "Project Red Dog" isn't a small deal. Far from it, the ultimate scope of Windows Azure should dwarf that of Microsoft's latest client OS launch in Vista. This is a play for the entire Web, from hosted enterprise applications and services to hobbyist stuff running over the wire.

Azure is Microsoft's ground-up, services-based foundation for cloud-based applications and infrastructures. As Kathleen Richards reports for Redmond Developer News, Azure provides an abstracted environment for deploying and managing highly scalable and available cloud-based applications.

Azure represents a sea change for Microsoft, a company that has famously struggled to come to terms with the very concept of services-based computing. Remember when Microsoft wouldn't even say the term SOA?

That era is over. Big time. Services will be a strategic focus in Redmond for the foreseeable future. From Windows to .NET Framework to SQL Server, SharePoint and Dynamics CRM, every corner of Microsoft's enterprise portfolio is going service-based. Microsoft even discussed an upcoming portal for Microsoft's System Center product, called "Atlanta," that leverages Azure to provide analysis and presentation of the status of on-premise infrastructure.

Despite all that, it was notable how closely Microsoft stayed to its tried and proven playbook.

Windows brand and platform leverage? Check. From the Azure name to the integration of the Hyper-V hypervisor virtualization, Microsoft went to great lengths to deeply brand Windows into this cloud platform.

Visual Studio and .NET integration? Check. Amitabh Srivastava's "Hello PDC" demo showed how Azure cloud-based applications could be written using the familiar ASP.NET in Visual Studio. Throughout the presentation, attendees were pitched on the benefits of familiar tooling and languages.

XML foundations? Check. Cloud models are built in XML, which enables all sorts of extensibility scenarios.

Questionable support for non-preferred Microsoft technologies? Oh, yes -- check. Support in Azure for unmanaged native code, Amitabh let slip late, will come later. There's certainly an openness and interoperability message, but it's hardly surprising that the early work will be happening inside the Microsoft toolshed.

While the direction Microsoft took here may not be a surprise, it's clear that the company is taking the long bet. PDC 2008 may be remembered as the pivot point, when Microsoft moved past the tension that's been building between shrink wrap and services. The bet is on. The infrastructure is being deployed and the tools are being mobilized.

Did you see the keynote? What are your thoughts on Windows Azure? E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 10/27/2008


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube