Cache Topology

Standalone This setup consists of a single node containing

all the cached data. It’s equivalent to a singlenode cluster and does not collaborate with

other running instances.

Distributed Data is spread across multiple nodes in a cache

such that only a single node is responsible for

fetching a particular entry. This is possible by

distributing/partitioning the cluster

in a balanced manner (i.e., all the nodes have

the same number of entries and are hence load

balanced). Failover is handled via configurable

backups on each node.

Replicated Data is spread across multiple nodes in a cache

such that each node consists of the complete

cache data, since each cluster node contains all

the data; failover is not a concern.

Caching Strategies

Read

Through

A process by which a missing cache entry is fetched from the integrated

backend store.

Write

Through

A process by which changes to a cache entry (create, update, delete) are

pushed into the backend data store.

It is important to note that the business logic for Read-Through and WriteThrough operations for a specific cache are confined within the caching layer

itself. Hence, your application remains insulated from the specifics of the

cache and its backing system-of-record.