JCache Configuration

You can create custom cache configurations associated with the names of JCache. The JCache data structures that do not have any configuration defined use the default configuration. If you want to set a configuration that is valid for all jcaches, you can name your configuration as default. A user-defined default configuration applies to every JCache that does not have a specific custom JCache configuration defined with the jcache’s name. You can also use wildcards to associate your configuration with multiple jcache names. See the configuration documentation for more information about wildcards.

Number of synchronous backups/replications. The higher the number, the more highly available cluster but performance decreases and memory cost of each entry increases. Synchronous backup operations have a blocking cost which may cause higher latencies.

Number of asynchronous backups/replications. The higher the number, the more highly available cluster but performance decreases and memory cost of each entry increases. Asynchronous backups are fire & forget and do not require acknowledgements.

Fully qualified class name of the cache key type. Its default value is java.lang.Object.

Fully qualified class name of the cache value type. Its default value is java.lang.Object.

Eviction policy that compares values to find the best matching eviction candidate. Its default value is LRU (less recently used).

Maximum size policy. If the maximum size is reached, the cache is evicted based on the eviction policy.

Maximum free/used percentage or maximum size in bytes depending on the selected maxSizePolicy.

Time-to-live for cache entries, in seconds.