Command Palette

Search for a command to run...

Hectal
Phase 0Beginner1 of 17 in Redis

Redis Foundations

What Redis really is, why it is fast, how a command travels through it, and how to name keys so the rest of the course has solid ground.

Most people meet Redis as "the cache". This phase replaces that with a better mental model: Redis is a server that holds data structures in memory and runs small, fast operations on them one at a time. Everything else in the course (caching, locks, rate limiters, queues, leaderboards) is built from that one idea.

You will set up a local lab you'll reuse in every later phase, see the protocol on the wire, learn the threading model precisely enough to reason about latency, and design keys the way production teams do.

0/5 · 0%
5 topics ~79 min 14 code blocks & diagrams
Start with the first topic
1
0.1

What Redis Is (and What It Isn't)

Redis is an in-memory data structure server: you send it small commands over TCP, and it runs them against strings, hashes, lists, sets, sorted sets, streams and more, one at a time. It can play many roles, but each role comes with different durability and consistency guarantees.

17 min 1 diagram 1 code practice

2
0.2

Why Redis Is Fast

Redis answers in microseconds because data lives in RAM, the structures are tuned for their operations, commands run on one thread without locks, and the event loop multiplexes thousands of connections. The network round trip, not Redis, is usually the biggest cost.

17 min 1 diagram 2 code practice

3
0.3

Your Redis Lab: Docker, redis-cli, Insight, and Valkey

Set up a local lab you'll reuse all course: Redis and Valkey in Docker, redis-cli fluency, RedisInsight for browsing, and the handful of commands that tell you what a server is and how it's configured.

14 min 3 code practice

4
0.4

How a Command Executes: RESP, the Event Loop, and Threads

A Redis command is a RESP message on a TCP socket. It's read and parsed, queued, executed on the main thread, and its reply is buffered back. Knowing this path tells you where latency comes from and why some operations block everyone.

15 min 1 diagram 2 code practice

5
0.5

Key Design: Names, Namespaces, Tenants, and Versions

Keys are Redis's only index, so their names are your schema. Good keys are predictable, namespaced, tenant-aware and versioned, and they're designed with cluster slots, memory and migrations in mind.

16 min 3 code practice