5.2. Local Mode
Using Red Hat JBoss Data Grid's local mode instead of a map provides a number of benefits.
Caches offer features that are unmatched by simple maps, such as:
- Write-through and write-behind caching to persist data.
- Entry eviction to prevent the Java Virtual Machine (JVM) running out of memory.
- Support for entries that expire after a defined period.
JBoss Data Grid is built around a high performance, read-based data container that uses techniques such as optimistic and pessimistic locking to manage lock acquisitions.
JBoss Data Grid also uses compare-and-swap and other lock-free algorithms, resulting in high throughput multi-CPU or multi-core environments. Additionally, JBoss Data Grid's Cache API extends the JDK's
ConcurrentMap, resulting in a simple migration process from a map to JBoss Data Grid.
5.2.1. Configure Local Mode
A local cache can be added to any cache container in both Library Mode and Remote Client-Server Mode. The following example demonstrates how to add the
local-cache element.
Procedure 5.2. The local-cache Element
<cache-container name="local"
default-cache="default"
statistics="true">
<local-cache name="default"
start="EAGER"
batching="false"
statistics="true">
<!-- Additional configuration information here -->
</local-cache>
The
local-cache element specifies information about the local cache used with the cache container using the following parameters:
- The
nameparameter specifies the name of the local cache to use. - The
startparameter indicates when the cache container starts, i.e. whether it will start lazily when requested or "eagerly" when the server starts up. Valid values for this parameter areEAGERandLAZY. - The
batchingparameter specifies whether batching is enabled for the local cache. - If
statisticsare enabled at the container level, per-cache statistics can be selectively disabled for caches that do not require monitoring by setting thestatisticsattribute tofalse.
Alternatively, create a
DefaultCacheManager with the "no-argument" constructor. Both of these methods create a local default cache.
Local and clustered caches are able to coexist in the same cache container, however where the container is without a
<transport/> it can only contain local caches. The container used in the example can only contain local caches as it does not have a <transport/>.
The cache interface extends the
ConcurrentMap and is compatible with multiple cache systems.
