Zum Hauptinhalt springen

Negotiate Cache TTL and Invalidation

Negotiate a cache-aside TTL using freshness, load, and invalidation risk.

nosql-databases5 min read

Ravi, product manager Ravi wants one long TTL for all product documents because database reads spiked last weekend. Proposed TTL 24h too broad for prices Stale risk $18k weekend pricing exposure Fallback TTL 5m for price cache Cache-aside decisions balance load saved against stale-data cost. Fresh but high DB load Cheap but stale risk Classify the data Name stale cost Pair invalidation with fallback TTL Ravi says: Can we just cache product documents for 24 hours?

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Kontakt aufnehmen