Real Redis sandbox
Every scenario runs an actual Redis instance in a container — not a multiple-choice quiz or a video.
Keep a cache and data store alive under load. Practice the Redis failures that page on-call — eviction storms, big keys, blocking commands, failover and stale reads — against a real Redis sandbox.
Run rillence redis · real Redis in Docker · deterministic scoring.
Boot a real Redis in a container, inject a realistic failure, and investigate with redis-cli or your own tooling. Deterministic scoring, zero production risk.
Every scenario runs an actual Redis instance in a container — not a multiple-choice quiz or a video.
Eviction storms, big keys, blocking commands, TTL leaks, failover and stale reads — injected into a live instance.
Get progressive hints while you investigate, a scorecard for your fix and a postmortem explaining the root cause.
Practice alone, onboard new engineers, or run repeatable internal Redis team drills.
The Redis failure modes engineers actually meet in production — from keyspace hygiene to cluster and failover.
Wrong DB, missing or short TTLs, namespace collisions, wrong key types and dangerous KEYS scans.
Eviction storms, OOM, wrong maxmemory policy, big strings/hashes/lists and fragmentation spikes.
Slow HGETALL, large LRANGE, SMEMBERS on huge sets, Lua and KEYS blocking the event loop.
Connection storms, pool exhaustion, pipelining gone wrong and client-side backpressure.
Fork latency on BGSAVE, AOF rewrite spikes, broken dumps and recovery from disk.
Stale caches, thundering herds, cache stampede and incorrect invalidation.
Replica lag, reading stale data from replicas and replication link failures.
Sentinel quorum, split-brain, failover that drops writes and misrouted clients.
Slot migration, MOVED/ASK storms, hot slots and resharding under load.
Consumer-group backlog, pending entries, lost messages and runaway queue growth.
ACL misconfig, unsafe commands, exposed instances and the FLUSHALL reflex.
Multi-cause GameDays that combine memory, latency and failover under pressure.
Run rillence redis to open the interactive REPL.
Pick a scenario from any track and boot an isolated Redis sandbox.
Connect with redis-cli — or any client you already use — and dig in.
Get deterministic Detect / Fix / Trap scoring and a postmortem.
One subscription covers every lab. Train your judgment in a safe sandbox, not in production.