All 15 Caching questions
More in Caching
What is the risk of caching sensitive or user-specific data with a shared cache key, and how do you avoid it? What is negative caching, and why might you deliberately cache the fact that a lookup returned 'not found'? What are the main cache invalidation strategies (TTL, write-through, cache-aside), and when is each appropriate? What is cache stampede (thundering herd), and how do you prevent it in a high-traffic Node.js service? What is the 'stale-while-revalidate' caching strategy, and how would you implement it for an API response? What is multi-tier caching (combining an in-memory L1 cache with a distributed L2 cache), and what problem does it solve? How would you implement a write-behind (write-back) caching strategy, and what durability risk does it introduce?
Advertisement
Back to results for “Caching with Redis”
Node.js › Caching

What is Redis's EXPIRE and how do TTL-based keys interact with Redis's own memory eviction policies under memory pressure?

Advanced

Answer

EXPIRE (or the EX option on SET) sets a time-to-live on a Redis key, after which Redis automatically removes it -- but under memory pressure Redis can also proactively evict keys earlier than expiration according a configured eviction policy (like allkeys-lru, evicting the least recently used key regardless of TTL, or volatile-lru, only evicting keys with a TTL set), which matters because caching data with no TTL under an allkeys policy could have any key evicted at any time.
await redis.set('session:abc123', sessionData, { EX: 3600 });

# redis.conf: only evict keys that have a TTL set, oldest-accessed first
# maxmemory-policy volatile-lru
# maxmemory 2gb
Real-world example A team configures their Redis instance with maxmemory-policy set to volatile-lru specifically because they store both cache data (with TTLs, safe to evict) and durable session data (without TTLs) in the same instance, ensuring memory pressure only ever evicts the cache entries.

Common follow-ups: What's the difference between 'noeviction' and 'allkeys-lru' policies, and what happens to write operations once Redis hits maxmemory under 'noeviction'?;Why might mixing cache data and durable data in the same Redis instance be considered risky regardless of eviction policy?

Caching with Redis;Databases & ORMs (MongoDB/Mongoose SQL/Sequelize)
All 15 Caching questions