WF4.0 Combat (20): Introduction to Windows Server AppFabric

The server system for Windows server AppFabric is a system designed primarily for private cloud computing. It will serve as a key product for Microsoft's future foray into the private cloud market, allowing users to create and maintain their own cloud computing system architecture.

This article will provide a brief introduction to Microsoft's server system, Windows Server AppFabric, and then an instance of implementing a WCF host to Windows Server AppFabric.

The Windows Server AppFabric is mainly divided into two sections:

AppFabric Caching Services

AppFabric Caching Services were originally code-named "Velocity". It speeds up frequent access to information. A major component of AppFabric Caching Services is the caching client. For example, a ASP.net page that accesses a cache cluster (the cache cluster) consisting of a large number of caching servers (cache server). Each caching server (cache server) runs a AppFabric Caching services instance to maintain some cached data. Each client cache can also maintain its own local cache. As shown in the following illustration:

When the client obtains some data for the first time, such as the ASP.net application user provides some information, or reads the information from the database, it may use the AppFabric Caching The Services Client class library holds a unique name and this information in the cache cluster (cached cluster). For the client, all cache servers in the cache cluster are a single logical store. What data is cached by the client that does not know or care about the physical server. By selecting, the customer can also store the data in its own local cache. The name of the data item is required when the client needs to access the same data item again. It checks the local cache first. If the data item is found, the cached value is used directly. If the data item is not in the local cache, it is found in the cache cluster. If the data item is found here, the client uses a cached value that is found from the cluster. For the client, all of this is transparent, requiring only the desired data items, AppFabric Caching Services to implement all the other features. If the data project does not have a local cache and is not found in the cache cluster, the customer needs to look elsewhere, such as the application's database.