Learn Redis Online — 8 Interactive Lessons with a Visual Key-Space Simulator

Redis is one of the most widely deployed pieces of backend infrastructure in the world — used as a cache, a session store, a message broker, a rate limiter, a leaderboard engine, and a job queue. Its command set is small and fast to learn, but the mental models behind the patterns — why TTL matters, how INCR avoids race conditions, when to use a Hash versus a String, why SETNX is the foundation of distributed locking — take longer to absorb from documentation alone. The Redis Playground gives you a visual, interactive environment to practice every core Redis pattern without installing Redis, Docker, or any backend tooling.

The playground simulates Redis key-value behavior entirely in the browser. Every command you run updates the live key-space table — you can see key names, stored values, data types, and TTL countdowns all at once. Command history logs every operation with its output and a state diff showing which keys were added, changed, or deleted. Expiring keys count down to zero in real time and disappear from the table, exactly as they would in a production Redis instance.

Key-Value Basics covers the three commands you will use on every Redis project: SET writes a value, GET reads it, and DEL removes it. The lesson introduces the key naming conventions used in production systems — user:42, session:abc123, feature:new-dashboard, page:/pricing — and explains why colons are used as namespace separators.

Expiration covers SET key value EX seconds (write with TTL), TTL key (read remaining seconds), EXPIRE key seconds (add or update expiration on an existing key), and PERSIST key (remove expiration). The TTL countdown in the key table makes expiration concrete — you can see session tokens, OTP codes, and temporary locks automatically clean up without any application code.

Caching Pattern simulates the cache-aside pattern that powers most Redis deployments: check Redis first (GET), return immediately on a hit, fetch from origin on a miss, write the result to Redis with a TTL (SET key value EX 60), and serve. The lesson shows cache hit, cache miss, and expiration as three distinct states so the lifecycle is clear before you implement it in an application.

Data Types covers all four compound Redis structures. Lists (LPUSH, RPUSH, LPOP, LRANGE) are ordered sequences used for queues, activity feeds, and browser history. Sets (SADD, SMEMBERS, SCARD, SISMEMBER, SREM) store unique unordered members — perfect for tags, follower lists, and unique visitor tracking. Hashes (HSET, HGET, HGETALL, HDEL, HKEYS, HVALS) map field names to values on a single key, making them ideal for user profiles, product data, and structured objects stored efficiently without JSON serialization. Sorted Sets (ZADD, ZRANGE, ZSCORE, ZRANK) store members with a numeric score for automatic ranking — the standard approach for leaderboards, priority queues, and time-series indexing.

Atomic Counters covers INCR, INCRBY, DECR, and DECRBY. Redis processes commands on a single thread, which means INCR is guaranteed atomic — two workers calling it simultaneously always receive different integers with no application-level locking required. This makes Redis the standard choice for page view counters, vote tallies, like counts, inventory deductions, and rate limit windows (INCR + EXPIRE on a per-user-per-minute key).

Conditional Writes covers SETNX (SET if Not eXists), EXISTS, and PERSIST. SETNX returns 1 if it wrote the key (key was absent) and 0 if it did not (key already existed). This atomic behavior is the foundation of distributed locks: only the first caller in a race wins the write. Combine with EX to auto-release the lock if the worker holding it crashes. EXISTS checks presence without fetching the value — useful for checking lock state or cache warmth without the overhead of reading the full value.

Key Inspection covers the introspection commands used for debugging and operations: KEYS * and KEYS pattern (glob matching with * and ?), TYPE key (returns string, list, set, hash, or zset), RENAME key newkey (atomic rename), MSET (write multiple key-value pairs in one roundtrip), and MGET (read multiple values in one roundtrip). MSET and MGET are important for performance — reading six keys with MGET takes one network roundtrip instead of six.

Pub/Sub covers SUBSCRIBE channel, PUBLISH channel message, and UNSUBSCRIBE. Redis Pub/Sub delivers messages to all current subscribers of a channel instantly. It is used for cache invalidation signals (publish "invalidate page:/pricing" when the product changes), live notification delivery, inter-service events in microservices architectures, and lightweight realtime data without a full message queue like Kafka or RabbitMQ.