What is a cache? Definition and product effects
A cache is a storage layer that keeps a copy of data already computed or fetched so it can be served faster next time. Caches exist at several levels: in the browser, on a CDN close to the user, in the application server or in front of the database. Each copy has a validity period, after which it must be refreshed.
Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.
Why it matters for a PM
Caching makes a product faster and cheaper to run, but it creates a gap between the real data and what users see. That is a product trade-off: a price, a stock level or an account balance cannot tolerate the same delay as a help page. The PM helps decide, data by data, how fresh it must be and what has to update immediately after a user action.
Example
After a release, some customers of an online store still see the old price of a discounted item. The page was cached on the CDN for an hour. The team keeps caching product pages but invalidates them on every price change, and recalculates the final price at checkout.
Key points
- Caches stack up: browser, CDN, application, database.
- A copy's time to live (TTL) sets the maximum acceptable delay.
- Invalidating the cache at the right time is often harder than adding it.
- Personal data must never sit in a cache shared between users.
Common mistakes
- Caching critical data, such as stock or a balance, with no invalidation rule.
- Concluding a fix failed when the user is actually seeing an old copy.
- Adding a cache to hide a slow query without looking for the cause.
Go further with Module
The courses and lessons that cover this concept:
Guides on this topic
- Write a spec for an AI coding agent
The sections of a spec a coding agent can execute without guessing, with a SPEC.md template.
- Claude Code for Product Managers
What a PM can do with Claude Code, the method and the guardrails, with a starter CLAUDE.md.