Administration guide > Plan the WebSphere eXtreme Scale environment
You can install WebSphere eXtreme Scale in a stand-alone environment, or you can integrate the installation with WAS.
For the best performance, catalog servers should run on different machines than the container servers.
If running the catalog servers and container servers on the same machine, then use separate installations of WXS for the catalog and container servers. By using two installations, you can upgrade the installation that is running the catalog server first.
Cache topology considerations
Your architecture can use...
- local in-memory data caching
- distributed client-server data caching
Each type of cache topology has advantages and disadvantages.
The caching topology you implement depends on the requirements of the environment and application.
Data capacity considerations
The following list includes items to consider for capacity planning...
Number of systems and processors How many physical machines and processors are needed in the environment? Number of servers How many eXtreme Scale servers to host eXtreme Scale maps? Number of partitions The amount of data stored in the maps is one factor in determining the number of partitions needed. Number of replicas How many replicas are required for each primary in the domain? Synchronous or asynchronous replication Is the data vital so that synchronous replication is required? Or is performance a higher priority, making asynchronous replication the correct choice? Heap sizes How much data will be stored on each server?
Parent topic:Plan the WebSphere eXtreme Scale environment
Hardware and software requirements
Cache topology: In-memory and distributed caching
Container servers, partitions, and shards