Track 2 · Building Blocks
Redis Field Guide
One thread, one RAM, a dozen data structures. Redis is fast because it does very little per command, and it is dangerous for the same reason. This page covers what each structure is for, what is atomic and what is not, how it survives a restart, and how to scale it without losing your data quietly.
Guide24 min read
On this page
- The KEYS command that froze the toss
- The simple version
- Why it is fast, and what that costs
- The data structures in one glance
- Going deeper, structure by structure
- What is atomic, and what is not
- Recipes with the traps removed
- Keys, namespaces and the commands to avoid
- Eviction and the maxmemory trap
- Pub/Sub or Streams?
- Persistence: what survives a restart
- Scaling: replicas, Sentinel and Cluster
- When Redis fits, and when it does not
- Lab: Redis in Docker, start to finish
- War room: the cache that was also the database
- Common traps
- Cross-questions I get asked