- Used Books
- Staff Picks
- Gifts & Gift Cards
- Sell Books
- Stores & Events
- Let's Talk Books
Special Offers see all
More at Powell's
Recently Viewed clear list
Used Trade Paper
Ships in 1 to 3 days
Other titles in the Patterns & Practices series:
Moving Applications to the Cloud on the Microsoft Azure Platformby Eugenio Pace
Synopses & Reviews
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.
Reese explains the differences between traditional server hosting and using Cloud services. He then provides practical guidelines for key decisions and planning required of system administrators.
Teach yourself how to build and host scalable applications in the cloud using the services and features of Windows® Azure™ — one step at a time. Ideal for those with fundamental programming skills, this tutorial provides practical, learn-by-doing exercises for mastering the entire Azure platform.
Discover how to:
This book is the second volume in a planned series about Windows Azure technology platform. Volume 1, Moving Applications to the Cloud on the Windows Azure Platform, provides an introduction to Windows Azure, discusses the cost model and application life cycle management for cloud-based applications, and describes how to migrate an existing ASP.NET application to the cloud. This book demonstrates how you can create from scratch a multi-tenant, Software as a Service (SaaS) application to run in the cloud by using the latest versions of the Windows Azure tools and the latest features of the Windows Azure platform. The book is intended for any architect, developer, or information technology (IT) professional who designs, builds, or operates applications and services that run on or interact with the cloud. Although applications do not need to be based on the Microsoft Windows® operating system to work in Windows Azure, this book is written for people who work with Windows-based systems. You should be familiar with the Microsoft .NET Framework, Microsoft Visual Studio® development system, ASP.NET MVC, and Microsoft Visual C#® development tool.
About the Author
Eugenio Pace works in the Software and Services group for the Microsoft® Architecture Strategy team. He develops architecture guidance to help ISVs, Hosters and Companies, build, run and consume software delivered as a service. His blog can be found at http://blogs.msdn.com/eugeniop/
Dominic Betts is an expert with the patterns & practices team & other Microsoft® groups.
Scott Densmore is an expert with the patterns & practices team & other Microsoft® groups.
Ryan Dunn is an expert with the patterns & practices team & other Microsoft® groups.
Masashi Narumoto is an expert with the patterns & practices team & other Microsoft® groups.
Matias Woloski is an Enterprise Architect at Southworks S.R.L. He's been involved in software development for 6 yeasr. Currently, he's working with the patterns & practices team at Microsoft® in a Scrum-driven project. He maintains a blog at http://blogs.southworks.net/mwoloski/
Table of 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
What Our Readers Are Saying
Computers and Internet » Networking » Virtual Networking