Client Side Caching


XAP supports client side caching of space data within the client application’s JVM. When using client-side caching, the user essentially uses a two-layer cache architecture: The first layer is stored locally, within the client’s JVM, and the second layer is stored within the remote master space. The remote master space may be used with any of the supported deployment topologies.

Dependencies
In order to use this feature, include the ${XAP_HOME}/lib/optional/near-cache/xap-near-cache.jar and ${XAP_HOME}/lib/optional/near-cache/xap-near-cache-spring.jar files on your classpath or use maven dependencies:

<dependency>
    <groupId>com.gigaspaces</groupId>
    <artifactId>xap-near-cache</artifactId>
    <version>12.2.0</version>
</dependency>
<dependency>
    <groupId>com.gigaspaces</groupId>
    <artifactId>xap-near-cache-spring</artifactId>
    <version>12.2.0</version>
</dependency>
See also:

For more information on dependencies see Maven Artifacts


Local Cache
A local cache allows the client application to cache recently used data at the client memory address and have it updated automatically by the space when that data changes.

Local View
A Local View allows the client application to cache specific data based on client’s criteria at the client memory address and have it updated automatically by the space when that data changes.

Client caching over the WAN
Client caching over the WAN.

Monitoring client side cache
Monitoring the Local View/Cache.


Additional Resources