Caching & Delivery

The application checks the cache first; on a miss it reads from the database, then populates the cache before returning the result.

The cache itself is responsible for loading data from the database on a miss, presenting a single unified read interface to the application.

The cache proactively refreshes entries before they expire, ensuring that frequently accessed data is always served from cache with consistently low latency.

Writes go directly to the database, bypassing the cache entirely; data only enters the cache when it is subsequently read, avoiding cache pollution from write-heavy data that is rarely read.

Writes go to the cache immediately and are asynchronously flushed to the database in the background, trading durability risk for dramatically lower write latency.

Every write goes to the cache and the backing database synchronously in a single operation, ensuring the cache is always consistent with the database.