Administration guide > Plan the WebSphere eXtreme Scale environment > Cache topology



Peer-replicated local cache

For a local WebSphere eXtreme Scale cache, ensure the cache is synchronized if there are multiple processes with independent cache instances. To do so, enable a peer-replicated cache with JMS.

WebSphere eXtreme Scale includes two plug-ins that automatically propagate transaction changes between peer ObjectGrid instances. The JMSObjectGridEventListener plug-in automatically propagates eXtreme Scale changes using Java™ Messaging Service (JMS).

Figure 1. Peer-replicated cache with changes that are propagated with JMS

JMS propagates changes among two ObjectGrid instances that are running in different JVMs. Each ObjectGrid instance is associated with an application.

If you are running a WAS environment, the TranPropListener plug-in is also available. The TranPropListener plug-in uses the high availability (HA) manager to propagate the changes to each peer eXtreme Scale cache instance.

Figure 2. Peer-replicated cache with changes that are propagated with the high availability manager

The <a href=HA manager propagates changes among two ObjectGrid instances that are running in different JVMs. Each ObjectGrid instance is associated with an application." />


Advantages


Disadvantages


When to use

This deployment topology should be used only when the amount of data to be cached is small (can fit into a single JVM) and is relatively stable.


Parent topic:

Cache topology: In-memory and distributed caching


Related concepts

Local in-memory cache

Distributed cache

Embedded cache

Multi-master data grid replication topologies