Product overview > Cache > Caching architecture > Caching topology



Local in-memory cache

In the simplest case, eXtreme Scale can be used as a local (non-distributed) in-memory data grid cache. The local case can especially benefit high-concurrency applications where multiple threads need to access and modify transient data. The data kept in a local eXtreme Scale grid can be indexed and retrieved using WebSphere eXtreme Scale's query support. The ability to query the data can help developers greatly when working with large in memory data sets versus the limited data structure support provided with the Java™ virtual machine (JVM), which is ready to use as is.

The local in-memory cache topology for eXtreme Scale is used to provide consistent, transactional access to temporary data within a single JVM.

Figure 1. Local in-memory cache scenario

Local in-memory cache scenario


Advantages


Disadvantages


When to use

The local, in-memory cache deployment topology should only be used when the amount of data to be cached is small (can fit into a single JVM) and is relatively stable. Stale data must be tolerated with this approach. Using evictors to keep most frequently or recently used data in the cache can help keep the cache size low and increase relevance of the data.


Parent topic:

Cache topology: In-memory and distributed caching


Related concepts

Peer-replicated local cache

Distributed cache

Embedded cache

Multi-master data grid replication topologies