to ensure consistency
SQL queries execution
e.g. on Java, available
How It Works
The read-through/write-through caching strategy can be
classified as an in-memory, data-grid type of deployment.
When Apache Ignite is deployed as a data grid, the application layer begins to treat Ignite as the primary store.
As applications write to and read from the data grid, Ignite ensures that all underlying external databases stay updated and are consistent with the in-memory data.
How It Works
Ignite integrates with many databases out-of-the-box and, in write-through or write-behind mode, can synchronize all changes to the databases.
The strategy also applies to ACID transactions: Ignite will coordinate and commit a transaction across its in-memory cluster as well as to a relational database.
Read-through capability implies that, if a record is missing from memory, a cache can read the data from an external database. Ignite fully supports this capability for key-value APIs.
When you use Ignite SQL, you must preload the dataset into memory—because Ignite SQL can query on-disk data only if the data is stored in native persistence.
When It Works
This strategy works well in two cases:
It’s usually assumed that changes will be fully replicated eventually and,
thus, the cache and the primary store will become consistent.
As users transition to digital channels, the load on the bank's systems has increased. Therefore, load reduction and system scaling are constant and top priorities.