Skill area
Keeping cached data fresh through TTLs, delete-on-write, versioned keys, event-driven invalidation, and stale-data controls.
Practice items tagged with Cache Invalidation.
Compares caching response-shaped read models with caching domain entities or raw database objects.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.
Compares cache-aside, read-through, and write-through by read and write ownership, freshness, failure behavior, invalidation, fallback, stampede control, and operational complexity.
Explains when local process memory is enough and when shared Redis-style caching is worth the extra dependency.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.
Explains delete-on-write, versioned keys, event-driven invalidation, and the race conditions around cache freshness.
Preparation paths where this taxonomy appears in the track scope.