Book Image

Microsoft Azure: Enterprise Application Development

Book Image

Microsoft Azure: Enterprise Application Development

Overview of this book

Microsoft's Azure platform has proved itself to be a highly scalable and highly available platform for enterprise applications. Despite a familiar development model, there is a difference between developing for Azure and moving applications and data into the cloud. You need to be aware of how to technically implement large-scale elastic applications. In this book, the authors develop an Azure application and discuss architectural considerations and important decision points for hosting an application on Azure. This book is a fast-paced introduction to all the major features of Azure, with considerations for enterprise developers. It starts with an overview of cloud computing in general, followed by an overview of Microsoft's Azure platform, and covers Windows Azure, SQL Azure, and AppFabric, discussing them with the help of a case-study. The book guides you through setting up the tools needed for Azure development, and outlines the sample application that will be built in the later chapters. Each subsequent chapter focuses on one aspect of the Azure platform—web roles, queue storage, SQL Azure, and so on—discussing the feature in greater detail and then providing a programming example by building parts of the sample application. Important architectural and security considerations are discussed with each Azure feature. The authors cover topics that are important to enterprise development, such as transferring data from an on-premises database to SQL Azure using SSIS, securing an application using AppFabric access control, blob and table storage, and asynchronous messaging using Queue Storage. Readers will learn to leverage the use of queues and worker roles for the separation of responsibilities between web and worker roles, enabling linear scale out of an Azure application through the use of additional instances. A truly "elastic" application is one that can be scaled up or down quickly to match resources to demand as well as control costs; with the practices in this book you will achieve application elasticity.
Table of Contents (23 chapters)
Microsoft Azure: Enterprise Application Development
Credits
About the Authors
Acknowledgement
Acknowledgement
About the Reviewer
Preface
Index

Azure Diagnostics­ under the hood


When we consider working with Azure diagnostics, we need to decide what to collect and how to store the collected data. The following table summarizes the information available to us:

Data

Collected by default

Role(s)

Storage

Storage location name

Windows Azure logs

Yes

Web, Worker

Table

WadLogsTable

IIS logs

Yes

Web

Blob

wad-iis-logfiles

Windows diagnostic logs

Yes

Web, Worker

Table

WadLogsTable

Failed request logs

No

Web

Blob

wad-iis-failedreqlogfiles

Windows event logs

No

Web, Worker

Table

WadWindowsEventLogsTable

Performance counters

No

Web, Worker

Table

WadPerformanceCountersTable

Crash dumps

No

Web, Worker

Blob

wad-crash-dumps

Custom error logs

No

Web, Worker

Blob

user defined storage

On a traditional Windows system, IIS logs, crash dumps and failed request logs would be stored in files. These three logs are referred to as Directory logs in Azure's jargon, and end up in blobs. Except for custom...