Book Image

Microsoft Windows Server AppFabric Cookbook

Book Image

Microsoft Windows Server AppFabric Cookbook

Overview of this book

Windows Server AppFabric provides a set of integrated capabilities that extend IIS and the Windows Server platform making it easier to build, scale and manage composite applications today. Windows Server AppFabric delivers the first wave of innovation within an exciting new middleware paradigm which brings performance, scalability and enhanced management capabilities to the platform for applications built on the .NET Framework using Windows Communication Foundation and Windows Workflow Foundation.'Microsoft Windows Server AppFabric Cookbook' shows you how to get the most from WCF and WF services using Windows Server AppFabric leveraging the capabilities for building composite solutions on the .NET platform. Packed with over 60 task-based and immediately reusable recipes, 'Microsoft Windows Server AppFabric Cookbook' starts by showing you how to set up your development environment to start using Windows Server AppFabric quickly. The book then moves on to provide comprehensive coverage of the most important capabilities provided by Windows Server AppFabric, diving right in to hands-on topics such as deploying WCF and WF applications to Windows Server AppFabric and leveraging the distributed caching, scalable hosting, persistence, monitoring and management capabilities that Windows Server AppFabric has to offer, with recipes covering a full spectrum of complexity from simple to intermediate and advanced.
Table of Contents (16 chapters)
Microsoft Windows Server AppFabric Cookbook
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface

Using AppFabric local cache


Along with server side in-memory caching, AppFabric also supports in-process client caching scenarios.

AppFabric local cache works as follows:

  • Local caching is configured on the client

  • Client requests for an object to be returned from a cache (for example, a Get call)

  • If the object is available in the local cache then a reference to the object is directly sent to the calling client (without looking up the server cache)

  • If the object is not available in-memory, then it is pulled from the server and it is placed in the local cache as well as returned back to the calling client

  • Any subsequent request to the same object will result in the object being retrieved from the local cache

  • The only exception, where the object will be requested from the server for the second time, is when it is invalidated from the local cache

Note

It must be considered that once the object is placed in the AppFabric's local cache, all the subsequent calls will use this version of the object, regardless...