Skip to content
Networking·Intermediate·Conceptual·1 min read

When is it appropriate to not cache a request?

Short interview answer

For data that must be exactly current at read time and has consequences if stale — a checkout's final price, an account balance, a permissions check — or for one-off actions. Even then, showing a cached value while revalidating can be acceptable if the authoritative check happens server-side at the decisive moment.

Key takeaway

Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.

← Back to Client-side data fetching patterns

Related questions