Redis Cache Lab

Experiment with high-speed memory, eviction, and TTL.

bolt

boltCache-Aside Pattern

This lab demonstrates the Cache-Aside pattern. When the application needs data, it first checks the Redis cache. If it's a Cache Miss, it fetches from the slower Database and then stores it in Redis for future requests. Subsequent requests result in a Cache Hit, serving data at memory speeds.

delete_sweep

delete_sweepLRU Eviction Policy

When the Max Memory is reached (8 items in this lab), Redis must make room for new data. This lab uses LRU (Least Recently Used). It tracks access timestamps and evicts the item that hasn't been used for the longest time, ensuring frequently accessed data stays in memory.

Memory Clusters (Max 8)

LRU Policy Active

add

Source Database

Protocol Logs

LIVE

System initialized. Use 'Fetch from DB' to see cache-aside logic.