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

Building a custom provider model


In this recipe we will implement an abstraction on top of Windows Server AppFabric Cache. The idea is to support:

  • Multiple implementations of a Cache provider

  • Ability to switch providers via configuration

As Windows Server AppFabric Cache is an external subsystem, it makes sense to have an abstraction around it and have the capability to plug in a suitable implementation at runtime.

Note

Consider a scenario for an ISV (Independent Software Vendor) where their application is built using Windows Server AppFabric Cache. One of their customers does not have Windows Server 2008 so they cannot install Windows Server AppFabric Cache. If ISV was able to implement a provider model such that they could switch Cache implementations via a configuration switch (for example, replacing Windows Server AppFabric Cache with ASP.NET's HttpCache) they would still be able to sell their product to this customer.

Of course, there is a feature cost associated with this type of generalization...