Redis Caching in NestJS: I Cut Database Calls by 60% in Production

It depends on the workload, but caching frequent read queries can cut database calls dramatically (here by around 60%) and reduce response times from hundreds of milliseconds to single digits.

Cache-aside means the app checks the cache first, and on a miss it loads from the database and writes the result back to the cache for next time.

Use TTLs for data that can be slightly stale, and explicitly invalidate or update cache entries when the underlying data changes to avoid serving outdated values.