Database Caching

Ignite database caching is implemented in the data grid component. It enables users to keep the most frequently accessed data in memory, by either partitioning or replicating it across a cluster of computers.

Write-Through & Read-Through

Whenever an update happens in the in-memory cache, Ignite can optionally propagate it to the underlying database. Also, whenever the data is requested from cache and is not there, Ignite can automatically load it from the underlying database. Such behavior is called write-through and read-through correspondingly.


In a simple write-through mode each cache put and remove operation will involve a corresponding request to the persistent storage and therefore the overall duration of the cache update might be relatively long. To mitigate such cases, Ignite offers an option to perform an asynchronous persistent store update also known as write-behind.

Automatic Persistence

Ignite ships with its own database schema mapping wizard which provides automatic support for integrating with persistence stores. This utility automatically connects to the underlying database and generates all the required XML OR-mapping configuration and Java domain model POJOs.

In-Memory Data Grid

See in-memory data grid for more information.