Loading
Topic
Invalidation after writes, versioned keys, stale data, event-driven invalidation, permission revocation, and derived cache freshness.
Practice items tagged with Cache Invalidation.
Compares server-controlled output caching with HTTP cache semantics and defines safe keys, variation, invalidation, identity, and multi-instance behavior.
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.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.