Client-Side Caching

GigaSpaces supports client-side caching of Space Where GigaSpaces data is stored. It is the logical cache that holds data objects in memory and might also hold them in layered in tiering. Data is hosted from multiple SoRs, consolidated as a unified data model. data within the client application's JVM Java Virtual Machine. A virtual machine that enables a computer to run Java programs as well as programs written in other languages that are also compiled to Java bytecode.. 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 $GS_HOME/lib/optional/near-cache/xap-near-cache.jar and $GS_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>16.4.0-m1</version>
</dependency>
<dependency>
    <groupId>com.gigaspaces</groupId>
    <artifactId>xap-near-cache-spring</artifactId>
    <version>16.4.0-m1</version>
</dependency>

Additional Resources

• For a detailed description of the different caching scenarios, refer to Caching Scenarios in the Product Overview.
• For more advanced WAN- based topologies see the Multi-Site Replication over the WAN section.