Kind of like I did with Virtualization some time ago, I’d like to introduce you to “Azure” with a primer (intro level) post. You know Microsoft and the TS2 team have been trying to educate you on Software + Services for some time now; helping you understand how the S+S strategy is different (and much better in our opinion) than SaaS – hopefully, you are already up-to-speed at least somewhat on that. What you’ll be hearing a LOT more about in the coming months is something called Azure, which is a part of our S+S story. Cloud based computing is here to stay and will be an increasingly greater component (e.g. BPOS) of future computing solutions for you and your customers, so let me try and give you the essential info you need to understand what Azure is and how it fits into the overall cloud picture…
Let’s start by differentiating between Windows Azure and the Azure Services Platform (ASP). Unfortunately, many will not be as informed as you are now and may not know the difference between the two, so when you see/hear the Azure term used, it’s important to ascertain if someone is talking about Windows Azure or ASP. For that, I’ll show a quick graphic that should bring this differentiation to light rather quickly and also will serve as good foundation for understanding the entire Azure system or platform.
As you can see from the graphic, the overall system consists of three basic layers with the bottom layer being Windows Azure (you will also hear the terms “fabric” and “Foundation services” used in conjunction with this layer). This is the basic “OS in the sky” that handles all the foundational computing needs of the services platform layer as well as the online services (end-user accessible) layer. The ASP, the middle layer as you can see, which rides on top of the Windows Azure layer, essentially provides the additional services, over and above the base OS (you will also hear the term “Building block services” used in conjunction with this middle layer), that will be leveraged by the online apps. The key thing here is that this layer does not provide a UI. That’s where the Online services layer (or “Finished services”) comes in. From a conceptual point of view, this is not all that different from an “on-premises” solution where you’ll have things like SQL servers, running on Windows Server, and providing the key database services for end-user applications like Sharepoint, or CRM, or other solutions that require an underlying database system. The main thing about these cloud based implementations is that you’re only ever paying for what you need and/or use, and there’s no on-premise infrastructure to have to purchase, build, and support. It also provides for very robust on-demand scalability and very high reliability and availability. The other key thing to know is this services platform is an extension of the .NET programming model and developers will be able to use existing skills with .NET and Visual Studio to access and leverage it. And, the services use industry standard SOAP, REST and XML protocols so using them won’t be a problem regardless of the operating system or programming language you’re using. Finally, one of the most significant aspects for S+S and our Azure platform is it’s integration with your existing or future on-premise solutions, it’s not an “either/or” proposition, which we think is a very compelling advantage over many SaaS solutions.
Well, this was just a primer, so I’ll stop here, even though I’ve barely scraped the surface of this topic, but hopefully, I given you enough so that you’ll have a clue now when someone mentions Windows Azure or Azure Services Platform. Here’s a link to some more info on Microsoft.com around the Azure platform and S+S: Azure Services Platform
And here’s an additional link to an interesting ComputerWorld article from last October (PDC) Ozzie details Azure, Microsoft's cloud version of Windows. And here’s a couple of key quotes from the article: “Windows Azure is the foundation of a new Azure Services Platform that is designed to compete with Amazon.com Inc’s Elastic Compute Cloud (EC2) service as a scalable application-hosting environment…“ and “The key element of Windows Azure is a Fabric Controller tool that "manages the life cycle" of online services…“.
Btw, one last note, you’ll also start hearing about something called Red Dog (in fact, Mary-Jo Foley is already blogging about it Red Dog: Can you teach old Windows hounds new tricks?). I would actually recommend her article, it’s a pretty interesting read about how Microsoft got going in the cloud computing game. The short take on RedDog is that it is part of the fabric and is how Microsoft will provide computing, storage, and management in the cloud.
And I just saw a ComputerWorld article that indicates we are planning to release this by year end.
Ballmer: Azure ready for release by end of year