Administration guide > Plan the WebSphere eXtreme Scale environment
Cache topology: In-memory and distributed caching
With WebSphere eXtreme Scale, the architecture can use...
eXtreme Scale requires minimal additional infrastructure, such as disk, to operate. The infrastructure consists of scripts to install, start, and stop a JEE application on a server.
Cached data is stored in the eXtreme Scale server, and clients remotely connect to the server.
When you deploy in a local, in-memory environment, 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.
When you deploy in a distributed environment, 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
- Peer-replicated local cache
- Distributed cache
- Embedded cache
- Multi-master data grid replication topologies
Parent topic:Plan the WebSphere eXtreme Scale environment
Hardware and software requirements
Container servers, partitions, and shards