在自动扩展任何应用服务时和之后的内存缓存行为 [英] Behavior of In-memory Cache while and after auto-scaling any app service

问题描述

在将应用服务自动扩展为>时，如何处理应用服务的内存缓存？是否执行了1个实例中的1个实例？

How in-memory cache of an app service is handled when auto-scaling of app service into > 1 instances from 1 instance is performed?

现有实例的所有内容是否都被复制到新创建的实例？

Does the all the content of existing instance gets copied to newly created instances?

是否创建了所有更改in实例缓存在自动缩放后反映在所有其他实例中？

Does all the changes created in on instance cache reflect in all the other instances after auto-scaling?

推荐答案

BDivya，

BDivya,

内存缓存是ASP.NET核心2.0或更高版本的一部分。你可以找到更多关于它的信息

这里。但是，内存不会随应用服务而扩展。为此你必须转移到

分布式缓存 由SQL或Redis支持。

In-Memory cache is part of ASP.NET core 2.0 or later. You can find more information about it here. In-memory does not however scale with an app service. For that you'll have to move to a distributed cache backed by SQL or Redis.

我希望这会有所帮助。如果没有，请随时详细说明您想要达到的目标，我可以提供更好的答案。

I hope this helps. If it doesn't, please feel free to elaborate on your what you're trying to achieve and I can provide a better answer.

这篇关于在自动扩展任何应用服务时和之后的内存缓存行为的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！