Concept
Write-through
With a write-through cache, every write goes to the cache and to the database before the caller is told it succeeded. Reads that follow find the new value already cached. It costs a slower write, in exchange for a cache that is not stale and a database that has every confirmed change.
Where you'll see it
Related concepts
Sources: Redis docs: persistence ↗ · AWS Builders' Library: Caching challenges and strategies ↗ · Uber: How Uber serves over 40 million reads per second with an integrated cache ↗ · Report a problem
The definition is in our own words; the sources are those of the lesson Write-through vs write-back.