There are several very large objects in our web application that we load into the cache from the database.
Our current strategy is great ... if you are not the user who starts the cache download. In this case, it was said about 5-10 seconds of additional loading time, which is unacceptable.
We currently receive this item every ~ 10 minutes.
What are the standard solutions to solve this problem now, I have the following two ideas.
You have an independent service that reloads cache items when they expire.
The cache object is infinite, always serving the last cached object, but updating the cached object in the partition for some time. (this is quite risky, although the object may be obsolete)
We also use ASP.NET MVC, Postgre SQL, and App Fabric, although I would expect this to not make much difference, as it is pretty theoretical.
source share