Caching Application block in Web farm environment

Topics: Caching Application Block
May 1, 2007 at 12:28 AM

How to use a caching application block in Web farm environment. please help us with example or links

May 1, 2007 at 5:17 PM
The caching block is designed to use an in-memory (per AppDomain) cache, with an optional write-through backing store. The backing store is designed to allow cache data to survive application restarts, but it will not allow sharing of cache data across multiple processes or machines. You can use the caching block in a web farm if you do not require all nodes to have the exact same cache data and expirations. This can be appropriate for rarely changing reference data, where it's more important for the data retrieval to be quick than to guarantee consistency. However if you need to guarantee that all nodes have the same data you should not use the caching block. Often the best solution is to store this data in a database, since you get the locking and transactional behaviors for free.

Jun 12, 2007 at 3:40 AM
How about hosting the caching system as a web service?
All your other app\web server will point to it for the caching service.
Dec 8, 2009 at 3:53 PM


if you host the web service in web farm you will have the same issue with synchronization, but on other application layer.