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 optimistic concurrency


Windows Server AppFabric allows cache clients (as long as they are authorized) to access and modify the cache concurrently. Concurrent cache read-access works just fine and the cache cluster (scale-out) generally helps with demands on the scalability. However, the real challenge is to handle concurrent writes to the cache.

Note

To understand concurrency issues, consider a scenario where we have two cache clients, let's call them client A and client B. Let us assume that client A and client B both have copies of the same data (retrieved against the same key from Windows Server AppFabric Cache). Imagine that client A updates the data in the cache. Now what would happen if client B tried to update the same data in the cache? Should client B override the value in the cache? Or should an exception be raised?

Windows Server AppFabric caching supports two modes to handle concurrency scenarios, namely Optimistic Concurrency and Pessimistic Concurrency. In this recipe...