Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Silverlight 5 and Windows Azure Enterprise Integration

You're reading from   Microsoft Silverlight 5 and Windows Azure Enterprise Integration A step-by-step guide to creating and running scalable Silverlight Enterprise Applications on the Windows Azure platform with this book and ebook

Arrow left icon
Product type Paperback
Published in Mar 2012
Publisher Packt
ISBN-13 9781849683128
Length 304 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
David Burela David Burela
Author Profile Icon David Burela
David Burela
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Microsoft Silverlight 5 and Windows Azure Enterprise Integration
Credits
About the Author
1. Acknowledgement
About the Reviewers
2. www.PacktPub.com
3. Preface
1. Getting Started 2. Introduction to Windows Azure FREE CHAPTER 3. Hosting Silverlight Applications in Azure 4. Using Azure Queues with Silverlight 5. Accessing Azure Blob Storage from Silverlight 6. Storing Data in Azure Table Storage from Silverlight 7. Relational Data with SQL Azure and Entity Framework 8. RIA Services and SQL Azure 9. Exposing OData to Silverlight Applications 10. Web-scale Considerations 11. Application Authentication 12. Using Azure AppFabric Caching to Improve Performance

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime