Windows Azure Architecture Guide Part 1 – Released
The Microsoft patterns & practices team are up to it again. Fresh on the heels of releasing the Developing Applications for SharePoint 2010 guidance, they’ve recently released part 1 of the Windows Azure Architecture Guidance.
What’s in the Windows Azure Architecture Guide – Part 1?
|The Guide||“Introduction to the Windows Azure Platform”provides an overview of the platform to get you started with Windows Azure. It describes web roles and worker roles, and the different ways you can store data in Windows Azure. It’s probably a good idea that you read this before you go to the scenarios.“The Adatum Scenario” introduces you to the Adatum company and the aExpense application. The following chapters describe how Adatum migrates the aExpense application to the cloud. Reading this chapter will help you understand why Adatum wants to migrate some of its business applications to the cloud, and it describes some of its concerns.
“Getting to the Cloud” describes the first steps that Adatum takes in migrating the aExpense application. Adatum’s goal here is simply to get the application working in the cloud, but this includes “big” issues, such as security and storage.
“How Much Will It Cost?” introduces a basic cost model for the aExpense application running on Windows Azure and calculates the estimated annual running costs for the application. This chapter is optional. You don’t need to read it before you go on to the following scenarios.
“Automating Deployment and Using Windows Azure Storage” describes how Adatum uses PowerShell scripts and the Microsoft Build Engine (MSBuild) to automate deploying aExpense to Windows Azure. It also describes how Adatum switches from using SQL Azure to Windows Azure Table Storage in the aExpense application and discusses the differences between the two storage models.
“Uploading Images and Adding a Worker Role” describes adding a worker role to the aExpense application and shows how aExpense uses Windows Azure Blob Storage for storing scanned images.
“Application Life Cycle Management for Windows Azure Applications” discusses how to manage developing, testing, and deploying Windows Azure applications. This chapter is optional. You don’t need to read it before you go on to the last scenario.
“Adding More Tasks and Tuning the Application” shows how Adatum adds more tasks to the worker role in the aExpense application. In this phase, Adatum also evaluates the results of performance testing the application and makes some changes based on the results.
|The companion samples||The samples illustrate all scenarios covered in the book. They provide a “single box” experience with minimal infrastructure requirements.|