howitworks.io logohowitworks
← Saari reels
BackendReel #44 · 10 Nov 2026

Redis itna fast kyun hai: interview ka poora jawab, 3 points mein

Redis fast hai teen wajah se, sirf in-memory hone se nahi. (1) Data RAM mein: main memory reference lagbhag 100 ns, disk seek lagbhag 8 ms (Peter Norvig ki table), toh disk wale database se hazaaron guna kam wait. (2) Single thread + event loop: Redis ka apna event library (Linux par epoll, Mac par kqueue) saare sockets ko ek saath dekhta hai, aur commands ek hi main thread par ek-ek karke chalti hain. Isliye locks nahi lagte aur har command atomic hai. Redis 6 se network I/O ke liye optional extra threads hain, par commands phir bhi ek main thread par chalti hain. (3) Data structure server: string, list, hash, set, sorted set built-in, toh leaderboard ya counter ke liye app mein code nahi likhna padta. Isi wajah se Redis cache, rate limiter aur leaderboard mein chalta hai. Neeche wala redis-demo.sh chaaron patterns redis-cli se chalata hai; humne 10 Nov 2026 ko Redis 8.10.1 par test kiya.

Links

Aaj ye karo

  1. Interview jawab, 3 points: RAM mein data (nanoseconds vs disk ke milliseconds), single thread + event loop (no locks, atomic commands), aur built-in data structures (string, list, hash, sorted set).
  2. Redis chalao: Mac par brew install redis, Ubuntu par sudo apt install redis-server, ya Docker: docker run -p 6379:6379 redis. Phir redis-cli PING, jawab PONG aana chahiye.
  3. Speed khud dekho: redis-benchmark -q -t get,set -n 100000. Humne Mac par GET lagbhag 2.3 lakh requests/second dekha. Aapka number machine ke hisaab se alag hoga.
  4. Atomic counter: INCR page:views. 100 clients ek saath 1000 INCR bhejein, value exactly 1000 aati hai, kyunki commands ek thread par ek-ek karke chalti hain.
  5. Leaderboard: ZINCRBY board 50 riya se score badhao, ZREVRANGE board 0 2 WITHSCORES se top 3 lo. Sorting Redis khud karta hai.
  6. Rate limiter: har request par INCR rl:user. Pehli request (value 1) par EXPIRE rl:user 60. Value limit se zyada ho toh 429 Too Many Requests bhejo. Window khatam hote hi key khud delete.
  7. Cache-aside: pehle GET user:42. Mil gaya toh wahi do (hit). Nahi mila (miss) toh database se laao aur SET user:42 value EX 300 se 5 minute ke liye Redis mein rakho.
  8. Script lo: redis-demo.sh download karke bash redis-demo.sh chalao. Ye sirf hiw:demo: wali keys banata aur end mein delete karta hai. Humne test kiya: counter 1000, request 101 par 429, cache pehle miss phir hit.
redis-benchmark -q -t get,set -n 100000
redis-cli INCR rl:karan # pehli baar: redis-cli EXPIRE rl:karan 60
redis-cli ZREVRANGE board 0 2 WITHSCORES
curl -O https://howitworksio.com/files/redis-demo.sh && bash redis-demo.sh

Sources

Redis docs (latency, event library, INCR, sorted sets, benchmarks), Peter Norvig latency table, Azure Architecture Center, MDN; redis-demo.sh aur redis-benchmark 10 Nov 2026 ko Redis 8.10.1 par chalaye.

Aise hi tech cases ke liye follow karo