Counter pattern in Redis - Step-by-Step Execution

Concept Flow - Counter pattern

Start

↓

Check if counter key exists

Yes↓

Increment counter by 1

↓

Return new counter value

↓

End

No↓

Create counter key with value 1

↓

Return 1

↓

End

The counter pattern checks if a key exists in Redis, increments it if yes, or creates it with 1 if no, then returns the current count.

Execution Sample

Redis

INCR page_views
INCR page_views
GET page_views

This code increments the 'page_views' counter twice and then retrieves its current value.

Execution Table

Step	Command	Key Exists?	Action	Counter Value After
1	INCR page_views	No	Create 'page_views' with 1	1
2	INCR page_views	Yes	Increment 'page_views' by 1	2
3	GET page_views	Yes	Retrieve 'page_views' value	2

💡 After step 3, the counter value is 2, showing two increments.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
page_views	null	1	2	2

Key Moments - 2 Insights

Why does the first INCR command create the key instead of failing?

In Redis, the INCR command automatically creates the key with value 1 if it does not exist, as shown in execution_table step 1.

What happens if we GET the counter before any INCR commands?

If the key does not exist, GET returns null or nil, meaning no value is set yet, unlike INCR which initializes it.

Visual Quiz - 3 Questions

Look at the execution table, what is the counter value after the first INCR command?

A null

B 0

C 1

D 2

💡 Hint

Check the 'Counter Value After' column in row 1 of the execution_table.

At which step does the counter key first exist in Redis?

A Step 3

B Step 1

C Step 2

D It never exists

💡 Hint

Look at the 'Key Exists?' column; it changes from No to Yes after step 1.

If we run INCR three times instead of two, what would be the counter value after step 3?

A 3

B 2

C 1

D 4

💡 Hint

Each INCR adds 1; see variable_tracker for increments after each step.

Concept Snapshot

Counter pattern in Redis:
- Use INCR key to increment a counter.
- If key doesn't exist, INCR creates it with 1.
- GET key retrieves current count.
- Useful for tracking counts like page views.
- Simple, atomic, and efficient increment operation.

Full Transcript

The Redis counter pattern uses the INCR command to increase a numeric value stored at a key. If the key does not exist, INCR creates it with the value 1 automatically. This pattern is useful for counting events like page views or clicks. The example increments the 'page_views' counter twice and then retrieves its value, which ends up as 2. The execution table shows each step's command, whether the key existed, the action taken, and the counter's value after the step. The variable tracker follows the 'page_views' value from null to 1, then 2. Key moments clarify why INCR creates the key and what happens if GET is called before any increments. The visual quiz tests understanding of the counter value after increments and when the key exists. This pattern is simple and efficient for counting in Redis.

Practice

1. What does the Redis command INCR do in the counter pattern?

easy

A. It increases the value of a key by 1.

B. It deletes the key from the database.

C. It sets the key to a specific string value.

D. It retrieves the current value of the key.

Solution

1. Step 1: Understand the purpose of INCR

   The INCR command is designed to increase the integer value stored at a key by 1.

2. Step 2: Compare with other commands

   Unlike GET which retrieves a value, or DEL which deletes a key, INCR modifies the value by incrementing it.

3. Final Answer:

   It increases the value of a key by 1. -> Option A

4. Quick Check:

   INCR means increment by 1 [OK]

Hint: INCR always adds one to the number stored [OK]

Common Mistakes:

• Thinking INCR deletes the key
• Confusing INCR with GET
• Assuming INCR sets a string value

2. Which of the following is the correct syntax to increment a counter named page_views in Redis?

easy

A. INCREMENT page_views

B. INCR('page_views')

C. increment page_views

D. INCR page_views

Solution

1. Step 1: Recall Redis command syntax

   Redis commands are issued as uppercase words followed by the key name without parentheses.

2. Step 2: Identify the correct command

   INCR page_views is the correct syntax; other options use invalid syntax or wrong command names.

3. Final Answer:

   INCR page_views -> Option D

4. Quick Check:

   Redis commands use space-separated syntax [OK]

Hint: Redis commands have no parentheses, just command and key [OK]

Common Mistakes:

• Using parentheses like a function call
• Typing 'increment' instead of 'INCR'
• Using lowercase command names

3. Given the following Redis commands executed in order:
INCR visits
INCR visits
INCR visits
GET visits
What will be the output of the last command?

medium

A. 3

B. 1

C. 0

D. Error

Solution

1. Step 1: Count increments

   Each INCR visits increases the value by 1. Three increments mean the value is 3.

2. Step 2: Retrieve the value

   GET visits returns the current value, which is 3 after three increments.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   3 increments = 3 [OK]

Hint: Count how many times INCR runs before GET [OK]

Common Mistakes:

• Assuming value starts at 0 without increments
• Confusing GET output with command name
• Expecting an error if key does not exist initially

4. You run the command INCR user_likes but get an error: "ERR value is not an integer or out of range". What is the most likely cause?

medium

A. The Redis server is down.

B. The key user_likes contains a non-integer value.

C. The command INCR is misspelled.

D. The key user_likes does not exist.

Solution

1. Step 1: Understand the error message

   The error says the value is not an integer or out of range, meaning the key exists but holds a non-integer.

2. Step 2: Check other options

   If the key did not exist, Redis would create it with value 1. Misspelling causes a different error. Server down means no response.

3. Final Answer:

   The key user_likes contains a non-integer value. -> Option B

4. Quick Check:

   INCR needs integer value to work [OK]

Hint: Check key's value type before INCR [OK]

Common Mistakes:

• Assuming key absence causes this error
• Thinking server down causes this error
• Ignoring value type requirements

5. You want to count unique visitors per day using Redis counters. Which approach correctly uses the counter pattern to track daily counts without mixing days?

hard

A. Use a list to store all visitor IDs and count its length.

B. Use a single key visits and reset it to zero every day at midnight.

C. Use keys like visits:2024-06-01, visits:2024-06-02 and increment each day separately.

D. Use INCR on a key named visits without any date information.

Solution

1. Step 1: Understand the need for daily separation

   To track counts per day, keys must be unique per day to avoid mixing counts.

2. Step 2: Evaluate options

   Using keys with date suffixes like visits:2024-06-01 keeps counts separate. Resetting a single key risks losing data if reset fails. Lists are not efficient counters. Using a single key mixes all days.

3. Final Answer:

   Use keys like visits:2024-06-01, visits:2024-06-02 and increment each day separately. -> Option C

4. Quick Check:

   Unique keys per day keep counts separate [OK]

Hint: Add date to key name for daily counters [OK]

Common Mistakes:

• Resetting counters can cause data loss
• Using single key mixes all days
• Using lists instead of counters