Book Image

Microsoft Silverlight 5 and Windows Azure Enterprise Integration

By : David Burela
Book Image

Microsoft Silverlight 5 and Windows Azure Enterprise Integration

By: David Burela

Overview of this book

Microsoft Silverlight is a powerful development platform for creating rich media applications and line of business applications for the web and desktop. Microsoft Windows Azure is a cloud services operating system that serves as the development, service hosting, and service management environment for the Windows Azure platform. Silverlight allows you to integrate with Windows Azure and create and run Silverlight Enterprise Applications on Windows Azure This book shows you how to create and run Silverlight Enterprise Applications on Windows Azure. Integrating Silverlight and Windows Azure can be difficult without guidance. This book will take you through all the steps to create and run Silverlight Enterprise Applications on the Windows Azure platform. The book starts by providing the steps required to set up the development environment, providing an overview of Azure. The book then dives deep into topics such as hosting Silverlight applications in Azure, using Azure Queues in Silverlight, storing data in Azure table storage from Silverlight, accessing Azure blob storage from Silverlight, relational data with SQL Azure and RIA, and manipulating data with RIA services amongst others.
Table of Contents (19 chapters)
Microsoft Silverlight 5 and Windows Azure Enterprise Integration
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface

Asynchronous processing and componentization


The ability of an application to scale in the cloud is vital when it comes to building large Internet applications. One way to ensure that an application is able to scale efficiently is by breaking it down into smaller, independent components, which operate asynchronously with each other.

Breaking a large application into functionally separate modules can have a number of benefits for the architecture of your application. They are as follows:

  • It allows the components to be scaled independently.

  • It reduces coupling within the application (when constructed with the messages and the interfaces). The components can then be updated separately.

  • It reduces the complexity by reducing the contact points to the business logic. The interactions must be explicit rather than a simple method call.

Having the components operate asynchronously with each other means the following:

  • The users and the User Interface (UI) are not being held up, waiting for the work to...