Build Redis (10 scenes)
Scene 01

Foundations — what Redis is, words you'll hear

Redis is an in-memory data-structure server: clients send commands over RESP to a single-threaded server, which mutates rich types (strings, lists, hashes, sets, sorted sets, streams) held in RAM and optionally persists snapshots/append-logs to disk.

Scene 01

Foundations — what Redis is, words you'll hear

  1. Watch
  2. Try it
  3. Predict
  4. Capture
service 1local maprestart wipes itservice 2local maprestart wipes itservice 3local maprestart wipes itCLIENTS · 3Service AclientSETService BclientLPUSHService CclientZADDRedissingle thread · in-memory keyspaceKEYSPACE · 6 keysSTRINGviews:home14823LISTfeed:42[a, b, c, …]HASHuser:42{name, email}SETonline{7, 14, 22}ZSETlb:global{…by score…}STREAMevents[t1, t2, …]optionalpersistenceRDB snapshotsnapshotpoint-in-timeAOF logappend-only logevery write
Backend services need rich shapes — recent items, leaderboards, online users — and lose them on restart, can't share across instances.
What to watch for

A quick three-beat tour. The problem first, then the architecture, then the words you'll need for the rest of the curriculum.

Continue unlocks when the animation finishes.
Sources

Where this sits in Build Redis

Scene 01 of 10, in the The loop act — One thread, one command — and the encoding under it.. An in-memory data-structure server, the eight core nouns, and the six canonical types. Orientation before you touch the internals.

Up next. One thread, one command — the architectural choice that makes Redis fast, and quietly explains every later trade-off in this curriculum.

All 10 scenes in Build Redis · Every curriculum

Designs that use this

Built with Arqly
Every scene in Build Redis builds on the one before it.All 10 Build Redis scenes