We have about 50 websites running in different application pools that are read from a common cache database (using the Microsoft Caching Caching application block).
We currently have a console application that populates the cache at 3 in the morning every morning. However, we want to get rid of this application and make the cache automatically update expired items using the ICacheItemRefreshAction interface.
We were going to create our cache object in Global.asax of each of the 50 websites. However, I am concerned that if we set the cache expiration policy in Global.asax, each 50 of the 50 websites will trigger an update action, resulting in data being overwritten 50 times.
We do not want only one website to set expiration policies, since then 49 other websites will be dependent on that one website and that architecture is no-no.
Given these limitations - any recommendations?
source
share