System design · Key technologies: the tools you will actually name

Redis: one thread, many jobs

Redis turns up in nearly every design as a cache, a counter, a leaderboard, a lock or a little queue, and each of those uses leans on the same two facts: every command runs alone on one thread, and the data lives in memory first and on disk second.

22 min read Full lesson in the app Patterns: sorted-set-leaderboard, atomic-counter, hash-slot

What you'll be able to do

Before this: caching-and-stampedes

Log in to read the rest of this lesson

Redis turns up in nearly every design as a cache, a counter, a leaderboard, a lock or a little queue, and each of those uses leans on the same two facts: every command runs alone on one thread, and the data lives in memory first and on disk second. This walkthrough runs about 22 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.

Log in to continue

The first module of every track is free to read on the web: see what's open in System design.