Product overview > Cache > Caching architecture
Cache topology: In-memory and distributed caching
With WebSphere eXtreme Scale, the architecture can use local in-memory data caching or distributed client-server data caching.
WebSphere eXtreme Scale requires minimal additional infrastructure to operate. The infrastructure consists of scripts to install, start, and stop a Java™ Platform, Enterprise Edition application on a server. Cached data is stored in the eXtreme Scale server, and clients remotely connect to the server.
In-memory environmentsWhen you deploy in a local, in-memory environment, WebSphere eXtreme Scale runs within a single JVM and is not replicated.
To configure a local environment you can use an ObjectGrid XML file or the ObjectGrid APIs.
Distributed environmentsWhen you deploy in a distributed environment, WebSphere eXtreme Scale runs across a set of JVMs, increasing the performance, availability and scalability. With this configuration, you can use data replication and partitioning. You can also add additional servers without restarting the existing eXtreme Scale servers. As with a local environment, an ObjectGrid XML file, or an equivalent programmatic configuration, is needed in a distributed environment. You must also provide a deployment policy XML file with configuration details
You can create either simple deployments or large, terabyte-sized deployments in which thousands of servers are needed.
- 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 JVM (JVM), which is ready to use as is.
- 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.
- Distributed cache
WebSphere eXtreme Scale is most often used as a shared cache, to provide transactional access to data to multiple components where a traditional database would otherwise be used. The shared cache eliminates the need configure a database.
- Embedded cache
WebSphere eXtreme Scale grids can run within existing processes as embedded eXtreme Scale servers or you can manage them as external processes.
- Multi-master data grid replication topologies
Using the multi-master asynchronous replication feature, two or more data grids can become exact mirrors of one other. This mirroring is accomplished using asynchronous replication among links connecting the data grids together. Each data grid is hosted in an independent catalog service domain, with its own catalog service, container servers, and a unique name. With the multi-master asynchronous replication feature, you can use links to interconnect a collection of these catalog service domains. Then, you can synchronize the catalog service domains with replication over the links. You can construct almost any topology because you choose how to define links among catalog service domains.
Parent topic:Cache architecture: Maps, containers, clients, and catalogs
Container servers, partitions, and shards
Configure distributed deployments
Configure local deployments