By default MashZone NextGen uses local memory for caching. This uses BigMemory as a local client that is installed with MashZone NextGen and requires only your MashZone NextGen license. In specific cases, you must also install BigMemory Servers on one or more additional hosts and configure MashZone NextGen and the Integrated MashZone Server to work with them. MashZone NextGen requires BigMemory Servers with a BigMemory license to support:
BigMemory Servers can be deployed in clusters, also known as Terracotta Server Arrays, that can easily be extended for scalable memory requirements.
With clusters, some of the internal MashZone NextGen caches must be distributed and managed by BigMemory Servers.
BigMemory Servers also can manage memory outside of heap both for better scalability and performance improvements.
BigMemory manages the In-Memory Stores created dynamically by other systems and makes connection information available to MashZone NextGen through the Terracotta Management Console (TMC) to allow MashZone NextGen to work with this data. Apama, for example, dynamically creates distributed stores for the Apama MemoryStore which MashZone NextGen can connect to and query.
MashZone feeds that use BigMemory connections as a data source.
See Configure BigMemory Servers for MashZone NextGen Caching and In-Memory Stores for instructions on configuring MashZone NextGen to work with BigMemory Servers.
You also need to provide configuration and connection information for In-Memory Stores that are created by other systems. For more information on these tasks, see:
See Caching for the MashZone NextGen Server for an overview of MashZone NextGen caching. For caching configuration, see Distributed Caching for MashZone NextGen Clusters.