- Windows Server AppFabric Caching
- WSAF Caching can maintain an in-process "local cache" in your cache client application to minimize deserialization and network overhead. Once an object is in the local cache, the AppFabric APIs will use that local copy exclusively until it is invalidated (either through a timeout or a notification). Objects in the local cache are therefore only loosely coherent with their master copies in the AppFabric cache hosts, so it is possible for the DataCache class to return stale objects to your application.
- ScaleOut StateServer
-
ScaleOut StateServer’s local cache is called the "client cache". Like AppFabric’s local cache, ScaleOut maintains it as in-process collection in order to minimize deserialization and network costs. However, the SOSS client cache is fully coherent and synchronized with the authoritative server—with every access, the client cache performs a quick version check with the ScaleOut host to ensure that it is returning the most recent version of an object to the caller. This provides several benefits:
- Objects returned by ScaleOut APIs are never stale.
- Applications can safely employ distributed, sequential logic (that is, when you change a cached object, all other clients in the farm will see the change immediately).
- Locking operations can be used in conjunction with the client cache.
- The ScaleOut ASP.NET session provider can safely use the client cache in all page requests, including those that use read/write session state.
