Moving Applications to the Cloud on the Microsoft Azure Platform

Description

How can a company's applications be scalable and have high availability?

 To achieve this, along with developing the applications, you must also have an infrastructure that can support them. For example, you may need to add servers or increase the capacities of existing ones, have redundant hardware, add logic to the application to handle distributed computing, and add logic for failovers. You have to do this even if an application is in high demand for only short periods of time. Life becomes even more complicated (and expensive) when you start to consider issues such as network latency and security boundaries.

 The cloud offers a solution to this dilemma. The cloud is made up of interconnected servers located in various data centers. However, you see what appears to be a centralized location that someone else hosts and manages. By shifting the responsibility of maintaining an infrastructure to someone else, you're free to concentrate on what matters most: the application. If the cloud has data centers in different geographical areas, you can move your content closer to the people who are using it most. If an application is heavily used in Asia, have an instance running in a data center located there. This kind of flexibility may not be available to you if you have to own all the hardware.

 Another advantage to the cloud is that it's a pay as you go proposition. If you don't need it, you don't have to pay for it. When demand is high, you can scale up, and when demand is low, you can scale back. Yes, by moving applications to the cloud, you're giving up some control and autonomy, but you're also going to benefit from reduced costs, increased flexibility, and scalable computation and storage. The Windows Azure Architecture Guide shows you how to do this.

CONTENTS:

ForewordForewordPrefaceAcknowledgmentsChapter 1: Introduction to the Windows Azure PlatformChapter 2: The Adatum ScenarioChapter 3: Phase 1: Getting to the CloudChapter 4: How Much Will It Cost?Chapter 5: Phase 2: Automating Deployment and Using Table StorageChapter 6: Phase 3: Uploading Images and Adding a Worker RoleChapter 7: Application Life Cycle ManagementChapter 8: Phase 4: Adding More Tasks and Tuning the ApplicationCreating a Cloud Project in Visual StudioUsing the Windows Azure Service Management APIUsing the Windows Azure Service Management CmdLets in a 64-bit EnvironmentUsing DNS with Windows AzureWindows Azure Storage Management ToolsCreating a Self-Signed Certificate for TestingGlossary