AliasSubRemoteCacheIgnite
This page provides generated reference documentation for the AliasSubRemoteCacheIgnite data model.
Overview
| Property | Summary |
|---|---|
| host | The host under which the database server, calendar backend, or other alias definitions are reachable. |
| maxLocalRecordCount | The size of the local near Cache. If the record limit is reached, elements will be removed from the cache using the LRE (Least Recently Used) strategy. |
| port | The port under which the database server, calendar backend, or other alias definitions are reachable. |
| useClientNearCache | If the Cached elements use case is more read heavy, using a near cache is expected to improve the speed from the second read request on (On the first call, the… |
host
Type: String
The host under which the database server, calendar backend, or other alias definitions are reachable.
maxLocalRecordCount
Type: Integer
Default: 100000
Requires: useClientNearCache property group
The size of the local near Cache. If the record limit is reached, elements will be removed from the cache using the LRE (Least Recently Used) strategy.
port
Type: String
The port under which the database server, calendar backend, or other alias definitions are reachable.
useClientNearCache
Type: Boolean
Default: false
If the Cached elements use case is more read heavy, using a near cache is expected to improve the speed from the second read request on (On the first call, the near cache loads the values from the cluster). If the usage is more write heavy, it may not result in a performance increase because of the additional synchronisation/write overhead.
Near caches are fully transactional and get updated or invalidated automatically whenever the data changes on the server nodes.