DCSIMG
What is not supported in AppFabric Azure Cache - Manu Cohen-Yashar's Blog

Manu Cohen-Yashar's Blog

What is not supported in AppFabric Azure Cache

Named Cache:
In Windows Server AppFabric Caching Service it is possible to create named caches and provide different configuration characteristics to each cache. For example, one cache with rarely changing data could have a very long time-to-live configured for cached data while another cache containing more temporary data could have a much shorter time-to-live. Furthermore, it is possible to create regions on a single node in the cache cluster and associate searchable tags with cache entries. Neither of these features are implemented in Azure AppFabric Caching which supports only the default cache!

Cache Notifications:
The Windows Server AppFabric Caching Service supports cache notifications which cache clients can subscribe to and receive notification when various operations are performed on the cache and the items contained in it. This feature is not supported in Azure AppFabric Caching Service.

Clusters:
The Windows Server AppFabric Caching Service runs on a cluster of servers that present a unified cache to the client. This service requires IT support to manage and configure the servers. These clusters can be quite large – the documentation, for example, describes the cache management needs of a cluster in the range of 50 cache servers. This IT need disappears in Azure AppFabric Caching since Microsoft handles all service management.

Manu

Comments

What is not supported in AppFabric Azure Cache – AppliSec « cache said:

Pingback from  What is not supported in AppFabric Azure Cache – AppliSec «  cache

# February 8, 2011 8:48 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: