CodeZettaInterview Hub

NestJS · Interceptors · Mid-Level · Debugging

Caching interceptor pitfalls?

Short Interview Answer

Caching personalized or authz-sensitive responses; weak keys; memory growth; stale data.

Detailed Explanation

Key by user/tenant when needed. Prefer HTTP/Redis caches with TTLs. Bypass on mutations.

Did you know this answer?