Design
Distributed Cache (Redis-like)
Design a distributed in-memory cache system supporting key-value operations, TTL, eviction policies, and consistent hashing.
01 - Why interviewers ask this
It requires you to reason about consistent hashing and node failure — a step up from a single-node LRU cache into genuine distributed-systems territory.
02 - Where this system exists in the real world
You interact with this design every day.
Redis Cluster / Memcached-style distributed caches
CDN edge caching layers
Database query-result caching layers
03 - What you'll master
Solve this once. Know it forever.
Apply consistent hashing for data distribution
Handle node failure and rebalancing
Choose eviction and replication strategies
04 - What you'll design
7 functional · 4 non-functional requirements.
GET, SET, DEL key-value operations
6 more requirements inside
Sign in to unlock the full brief and start designing
05 - Companies that ask this
You may face this exact question in your next interview.
Ready?
Open the canvas.
Design it yourself.
See all requirements, use staged hints, run your code, and compare with community discussions - all on the same canvas.
Start SolvingMore in Infrastructure