Summary: Space Caching policies and External Data Source

Overview

This section describes two Space Caching policies for an External Data Source:

  • All In Cache
  • LRU Caching

All In Cache

With an All In Cache, the Space holds all the data in memory.
In this case, the space connects to the datasource at startup, and loads all the data.
If data is changed in the space it is updated in the data source.
All data reads are in memory, since the data in memory and in the data source are identical.
See How to configure space caching policy to All In Cache

LRU Caching

With LRU caching, the Space holds only the most recent data. The amount of data is limited by the cache size.
In this case, the space connects to the datasource at startup, and loads data up to the defined cache size.

You can customize what data is loaded and how. See How to Customize Initial Load

If data is changed in the space, it is updated in the data source.
On data read, the data is first searched in memory. If it is not found, the datasource will be queried.
See. How to configure space caching policy to LRU

GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence