When and why use cache regions and named caches

Dec 15, 2010 at 4:41 PM

Why i should use named caches and region. Could you be so kind and describe it in short. So questions are: why do i need to create named caches and regions.

Dec 16, 2010 at 4:36 PM

Named Cache:  Think of it as a Database.
Region: Think of it as a table.
Cache Entry:  An entry into the region (even if you don't mention a region, AppFabric actually puts it into a system created region)

Since, AppFabric is seen as a Enterprise level Distributed Cache Framework, therefore, many applications can share the same AppFabric store.  In that case, there may be chances of collisions of key names, different requirements for configuration (e.g. Cache Eviction Algorithm, Time-To-Live, Notification support), etc which has resulted in creating "Named Cache".
For, Regions, it is more of categorization of related cache entries.  For example, one can group all cache entries related to "Customers" in a separate region called "customers".
 
I would love to hear from you about the performance and\or issues in this product.  Please do share them with me!
 
Hope it helps!