Hi all, has anyone tried using Redis Cache (or another distributed cache) to store the Memory Cahce/NuCache when auto scaling out? One of the issues with scaling out an Umbraco Azure web app instance is that each new instance will slam the database as it builds it's Memory/NuCache, so moving the memory cache into a distributed cache would hopefully alleviate this issue. (at least in theory lol) Has anyone tried this or something similar? Also posted on Our: https://our.umbraco.com/forum/using-umbraco-and-getting-started//112967-nucache-plus-redis-cache-for-automatic-scale-out

Is this something that @nzdev maybe has a strategy for? In the future we'll only selective load things in cache but I think that's a few major releases away still.

Nothing public. I did raise a few prs that never got in to customize the cache implemention.

maybe some pointers here? https://umbraco.com/blog/introducing-redis-and-azure-cognitive-search-to-the-umbraco-marketplace/ in the implementing a redis cache?

Thanks all! I'm definitely looking forward to the future lazy loaded cache 😄 and that would likely mitigate the issue of the app instances slamming the db when they start up, but it would still be nice if they had access to some distributed cache so they don't need to rebuild it as requests come in. I did read that blog posts about the marketplace's use of redis cache, when I was looking into this, and the response caching looks really good! but it unfortunately doesn't solve the issue of new instances needing to load their memory cache on boot. But maybe, coupled with the future lazy loaded cache implementation, this could work quite well!