Intermediate · 5h · 17 lessons
Redis
Blazing-fast in-memory data — types, caching, TTL, pub/sub, and persistence.
What you'll learn
- ✦Explain what an in-memory key-value store is, and decide when Redis belongs beside a main database
- ✦Choose and use the right Redis type (string, list, hash, set or sorted set) for a feature
- ✦Build a cache-aside layer and give keys a TTL so they expire on time
- ✦Write atomic counters and transactions that stay correct when many clients write at once
- ✦Send and receive events with pub/sub, and decide when Streams fit better
- ✦Explain persistence, eviction and clustering, and pick settings that fit an app
Part of these career paths
- Backend Developer path · course 10 of 14
Certification projects
Build 4 projects to earn your certificate
Hands-on work that proves you can apply what you learned — part of the certificate requirements.
Syllabus
Module 1 · 58m
Meet Redis Free
What you'll be able to do
- Can explain why Redis answers reads so fast, and what "in-memory" does and doesn't mean
- Can store and read strings with SET, GET and NX, using clear key names
- Can decide which data belongs in Redis and which must stay in the main database
Module 2 · 51m
Core data types Locked
What you'll be able to do
- Can pick the right type (string, list, hash, set or sorted set) for a feature
- Can build a first-in, first-out queue with a list and change one field of a hash
- Can use set operations to find overlaps, differences and unique counts
Module 3 · 57m
Caching & expiry Locked
What you'll be able to do
- Can build a cache-aside read path and keep it fresh with delete-on-write and a TTL
- Can set, check and debug expiry with EX, EXPIRE and TTL
- Can count safely with INCR and build a fixed-window rate limit
Module 4 · 54m
Messaging & atomicity Locked
What you'll be able to do
- Can send and receive live events with PUBLISH and SUBSCRIBE, and say when a missed message is acceptable
- Can group commands with MULTI and EXEC, predict what happens when one fails, and use a Lua script for check-then-change
- Can use a stream and a consumer group so no message is lost while a worker is down
Module 5 · 47m
Persistence & memory Locked
What you'll be able to do
- Can choose RDB, AOF or both, and work out how many writes a crash could lose
- Can set maxmemory and pick an eviction policy for a cache, a queue or a mix
- Can explain replicas versus shards, predict what a failover loses, and group keys with hash tags
Module 6 · 33m
Using Redis well Locked
What you'll be able to do
- Can match a feature to the Redis pattern and type that fits it, such as shared sessions or a flash-sale counter
- Can run Redis safely in production: SCAN instead of KEYS, pipelining for bulk work, limits and access control
- Can plan a next project that keeps the truth in a database and uses Redis for speed