Why caching patterns matter in Redis - Visual Breakdown

Concept Flow - Why caching patterns matter

Request comes in

↓

Check Cache

↓

Return

↓

Store in Cache

↓

Return

When a request comes, the system first checks the cache. If data is found (hit), it returns quickly. If not (miss), it fetches from the database, stores it in cache, then returns.

Execution Sample

Redis

GET user:123
IF cache miss THEN
  FETCH user from DB
  SET user:123 in cache
RETURN user data

This shows a simple cache lookup: try to get user data from cache, if missing, get from database and save in cache.

Execution Table

Step	Action	Cache State	DB Access	Result
1	Request user:123	Empty	No	No data yet
2	Check cache for user:123	Empty	No	Cache miss
3	Fetch user:123 from DB	Empty	Yes	User data fetched
4	Store user:123 in cache	user:123=data	No	Cache updated
5	Return user data	user:123=data	No	User data returned
6	Next request user:123	user:123=data	No	Ready to check cache
7	Check cache for user:123	user:123=data	No	Cache hit
8	Return user data	user:123=data	No	User data returned quickly

💡 Execution stops after returning user data on cache hit or after caching data on miss.

Variable Tracker

Variable	Start	After Step 4	After Step 8
Cache	Empty	user:123=data	user:123=data
DB Accessed	No	Yes	No
User Data Returned	No	Yes	Yes

Key Moments - 3 Insights

Why do we check the cache before the database?

Because checking the cache is faster and reduces load on the database, as shown in execution_table steps 2 and 7 where cache hit avoids DB access.

What happens when the cache misses?

The system fetches data from the database and then stores it in the cache, as seen in steps 3 and 4.

Why is caching important for repeated requests?

Because after the first miss, subsequent requests hit the cache (step 7), returning data faster without DB access.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the cache get updated with user data?

A Step 2

B Step 6

C Step 4

D Step 8

💡 Hint

Check the 'Cache State' and 'Action' columns around step 4.

At which step does the system avoid accessing the database due to a cache hit?

A Step 7

B Step 5

C Step 3

D Step 2

💡 Hint

Look for 'Cache hit' and 'DB Access' marked 'No' in the table.

If the cache was never updated, what would happen on step 7?

A Cache hit, data returned quickly

B Cache miss, DB accessed again

C Error because cache is empty

D Data returned from cache anyway

💡 Hint

Refer to the cache state in variable_tracker and execution_table steps 2 and 7.

Concept Snapshot

Caching Pattern:
1. Check cache first.
2. If miss, fetch from DB.
3. Store result in cache.
4. Return data.
Benefits: faster response, less DB load.

Full Transcript

This visual trace shows why caching patterns matter. When a request for user data comes in, the system first checks the cache. If the data is not there (cache miss), it fetches from the database and stores the data in the cache. Next time, the cache has the data (cache hit), so the system returns it quickly without hitting the database. This reduces database load and speeds up responses. The execution table tracks each step, showing cache state, database access, and results. The variable tracker shows how cache and database access change over time. Key moments explain why checking cache first is important, what happens on a miss, and why caching helps repeated requests. The quiz tests understanding of these steps. The snapshot summarizes the caching pattern in simple steps.

Practice

1. Why is caching important in Redis when building applications?

easy

A. It slows down the application by adding extra steps

B. It permanently saves all data without expiration

C. It deletes all data immediately after storing

D. It stores data temporarily to make data retrieval faster

Solution

1. Step 1: Understand caching purpose

   Caching temporarily stores data to reduce the time needed to get it again.

2. Step 2: Identify correct caching behavior in Redis

   Redis caching speeds up apps by storing data for quick access, not permanent saving or immediate deletion.

3. Final Answer:

   It stores data temporarily to make data retrieval faster -> Option D

4. Quick Check:

   Caching = Temporary fast storage [OK]

Hint: Caching means temporary storage for speed, not permanent save [OK]

Common Mistakes:

• Thinking caching saves data permanently
• Believing caching slows down the app
• Confusing caching with immediate data deletion

2. Which Redis command correctly sets a key with an expiration time of 60 seconds?

easy

A. GET key EX 60

B. SET key value EX 60

C. DEL key 60

D. EXPIRE key SET 60

Solution

1. Step 1: Recall Redis syntax for setting key with expiration

   The correct command is SET with EX option to set expiration in seconds.

2. Step 2: Check each option's correctness

   SET key value EX 60 uses SET key value EX 60 which is valid. Others misuse commands or order.

3. Final Answer:

   SET key value EX 60 -> Option B

4. Quick Check:

   SET with EX sets key and expiration [OK]

Hint: Use SET with EX to set expiration in seconds [OK]

Common Mistakes:

• Using GET instead of SET to set values
• Misplacing EXPIRE and SET commands
• Trying to delete keys with expiration time

3. Given this Redis command sequence:
SET user:1 "Alice" EX 10
GET user:1
What will the GET command return if run 15 seconds after the SET?

medium

A. nil

B. Empty string

C. Error: key expired

D. "Alice"

Solution

1. Step 1: Understand expiration effect

   SET with EX 10 means key expires after 10 seconds, so after 15 seconds key is gone.

2. Step 2: Predict GET result after expiration

   GET on expired key returns nil (no value), not error or empty string.

3. Final Answer:

   nil -> Option A

4. Quick Check:

   Expired key returns nil on GET [OK]

Hint: GET returns nil if key expired before access [OK]

Common Mistakes:

• Expecting old value after expiration
• Thinking GET returns error on expired keys
• Confusing empty string with nil

4. You wrote this Redis code:
SET session:123 "active"
EXPIRE session:123 0
What is the problem with this code?

medium

A. EXPIRE command syntax is incorrect

B. Key will never expire because 0 means infinite

C. Expiration time 0 deletes the key immediately

D. SET command must include expiration time

Solution

1. Step 1: Understand EXPIRE with 0 seconds

   EXPIRE with 0 seconds deletes the key immediately.

2. Step 2: Identify the effect on the key

   After EXPIRE session:123 0, the key is deleted immediately, which may be unintended.

3. Final Answer:

   Expiration time 0 deletes the key immediately -> Option C

4. Quick Check:

   EXPIRE 0 deletes key immediately [OK]

Hint: EXPIRE 0 deletes key immediately [OK]

Common Mistakes:

• Thinking EXPIRE 0 removes expiration (never expires)
• Assuming EXPIRE syntax is wrong
• Believing SET must always have expiration

5. You want to cache user profile data in Redis but ensure it updates if the user changes their info. Which caching pattern is best?

hard

A. Set key with expiration and delete key on user update

B. Set key without expiration and never delete it

C. Set key with very long expiration and ignore updates

D. Do not cache user data at all

Solution

1. Step 1: Understand caching with data freshness

   To keep data fresh, cache keys should expire and be deleted when data changes.

2. Step 2: Evaluate options for update handling

   Set key with expiration and delete key on user update uses expiration and deletes key on update, ensuring fresh data. Others risk stale data or no caching.

3. Final Answer:

   Set key with expiration and delete key on user update -> Option A

4. Quick Check:

   Expire + delete on update keeps cache fresh [OK]

Hint: Expire keys and delete on update to keep cache fresh [OK]

Common Mistakes:

• Not deleting keys on data change
• Using no expiration causing stale cache
• Avoiding caching user data unnecessarily