Master Redis Interview Questions: From Basics to Advanced, Ace Your Interview

Redis is a high‑performance, in‑memory key‑value store widely used for caching, message queues, and leaderboards. To help candidates succeed in technical interviews, this guide presents a comprehensive set of high‑frequency Redis questions and answers.

1. Basics

What is Redis and its main features? Redis (Remote Dictionary Server) is an open‑source, memory‑based key‑value store supporting multiple data structures. Its key features are high performance (in‑memory reads/writes), persistence to disk, rich data structures (strings, hashes, lists, sets, sorted sets), and high availability via replication, sentinel, and cluster modes.

Difference between Redis and Memcached

Data structures: Redis supports many, Memcached only simple key‑value pairs.

Persistence: Redis provides it, Memcached does not.

Performance model: Redis uses a single‑threaded model suitable for complex operations; Memcached uses multithreading for simple key‑value storage.

Cluster support: Redis has native clustering; Memcached requires client‑side sharding.

2. Data Structures

Supported data structures : String, Hash, List, Set, Sorted Set.

Maximum size of a Redis string : 512 MB.

List vs. Set

List: ordered, allows duplicates, supports bidirectional operations (e.g., LPUSH, RPOP).

Set: unordered, no duplicates, supports set operations such as intersection and union.

3. Persistence

Persistence mechanisms

RDB (snapshot): periodically writes memory data to a binary file.

AOF (append‑only file): logs every write operation and replays the log on restart.

Pros and cons

RDB: compact file and fast recovery; risk of data loss since the last snapshot.

AOF: higher data safety with second‑level durability; larger file size and slower recovery.

Choosing between RDB and AOF

Prefer AOF when data safety is critical.

Prefer RDB for higher performance when occasional data loss is acceptable.

Both can be enabled simultaneously to balance performance and safety.

4. High Availability & Clustering

Master‑slave replication

Master handles writes and propagates them to slaves.

Slaves handle reads and receive data from the master.

Benefits: read/write separation for performance and data backup for availability.

Sentinel mode

Monitors health of master and slaves.

Automatically elects a new master on failure.

Notifies clients of failover events.

Redis Cluster

Implements sharding to distribute data across multiple nodes.

Each shard has replicas; if a master fails, a replica takes over, ensuring high availability.

5. Performance Optimization

Use connection pools to reduce connection overhead.

Batch operations with MGET and MSET to lower network cost.

Set appropriate expiration times to avoid excessive memory usage.

Employ pipelines to minimize round‑trip latency.

6. Memory Eviction Policies

noeviction – rejects writes when memory is full.

allkeys‑lru – evicts the least recently used key among all keys.

volatile‑lru – evicts the least recently used key among keys with an expiration.

allkeys‑random – randomly evicts any key.

volatile‑random – randomly evicts a key with an expiration.

7. Practical Troubleshooting

Slow query analysis : use the SLOWLOG command.

Monitoring : tools such as Redis Monitor or Prometheus provide real‑time metrics.

Memory inspection : MEMORY USAGE reveals per‑key memory consumption.

Handling large keys

Split large keys into smaller ones.

Choose suitable data structures (e.g., store objects in a hash instead of a large string).

Periodically clean up unused large keys.

By mastering these topics, candidates can not only answer interview questions confidently but also apply Redis effectively in real‑world projects.