database caching is implemented in the
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
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
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.
See data grid for more information.