What is redis? why is it used? what problems does it solve?
Redis, short for Remote Dictionary Server, is an open-source, in-memory data structure store. It can function as a database, cache, and message broker. Redis is known for its speed and versatility, as it stores data in memory rather than on disk, enabling extremely fast read and write operations.
- 1
Caching: It reduces the load on databases by storing frequently accessed data in memory, improving application performance.
- 2
Session Management: Ideal for storing user session data in web applications.
- 3
Real-Time Analytics: Used in applications like leaderboards, tracking, and monitoring systems.
- 4
Message Queues: Acts as a message broker for pub/sub messaging patterns.
- 5
Data Structures: Supports advanced data types like strings, hashes, lists, sets, sorted sets, bitmaps, and more.
Scenario Questions
0-2 years experience
- 1How would you use Redis to cache the result of a database query in a web service? Walk me through the steps.
- 2If you set a key in Redis without an expiration and the application restarts, what happens to that key?
2-5 years experience
- 1We added Redis as a session store, but after a deployment some users see 'session not found' errors. What could be causing this and how would you troubleshoot?
- 2Explain the trade‑offs between using Redis as a simple key‑value cache versus using its built‑in LRU eviction policies for a high‑traffic product page.
5-8 years experience
- 1Design a rate‑limiting solution for an API using Redis. What data structures would you choose and how would you handle burst traffic?
- 2Our service needs to broadcast real‑time updates to thousands of clients. How would you leverage Redis Pub/Sub, and what are its limitations at scale?
8+ years experience
- 1We are planning to migrate a legacy monolith's caching layer to a multi‑region Redis cluster. What architectural considerations, data consistency models, and operational challenges would you address?
- 2How would you evaluate whether to replace Redis with a different store (e.g., Cassandra or DynamoDB) for a globally distributed, write‑heavy workload?
Follow-up Questions
- What factors would lead you to choose Redis over a traditional relational cache?
- Can you describe a scenario where Redis' persistence could become a bottleneck?
- How does Redis' single‑threaded model affect its performance characteristics?