caching - Difference between in-memory-store and managed-store in mule cache

Question

What are the main differences between in-memory-store and managed-store in mule cache scope and which gives a best performance.

What is the best way to configure caching in global scope?

We are currently using in-memory-store caching. We are always getting issues with memory outage as we are using a server with less HW configurations. We are using mule 3.7v.

Please provide your suggestions to configure cache in optimized way.

We are facing issue with cache expiration with in-memory-store. cache date is not being expunged after expiration time also. But when we use "managed-store" its working as expected. Below is my configuration:

Answer 1

内存中： 这将数据存储在系统内存中。内存中存储的数据是非持久的，这意味着在 API 重启或崩溃的情况下，缓存的数据将丢失。

托管存储： 这将数据存储在由 ListableObjectStore 定义的位置。Managed-store 存储的数据是持久的，这意味着在 API 重启或崩溃的情况下，缓存的数据不会丢失。

来源（详细说明与配置差异）： http ://www.tutorialsatoz.com/caching-in-mule-cache-scope/

Answer 2

我的一位朋友清楚地向我解释了这种差异，如下所示：

内存缓存--> 这是一个临时内存存储区域，它将存储数据。例如：考虑在Mule中使用VM组件，数据会以内存队列的形式存储在VM中

在托管存储的情况下——>我们可以存储数据并在以后的阶段使用它。示例：对象存储

主要是缓存会存储经常使用的数据。它将通过将常用数据或结果保存在缓存范围内来减少 db 或 http 调用。

但两者都仅用于临时存储，这意味着它们仅对特定会话有效。