Counter pattern in Redis - Mini Project: Build & Apply

Implementing a Counter Pattern in Redis

📖 Scenario: You are building a simple web application that tracks how many times a specific page has been visited. To do this efficiently, you decide to use Redis as a fast in-memory database to store and update the visit count.

🎯 Goal: Build a Redis counter that increments the number of visits each time the page is accessed.

📋 What You'll Learn

Create a Redis key to store the visit count with an initial value.

Set a threshold variable to define when to log a message.

Increment the visit count using the Redis INCR command.

Add a final step to check if the count reached the threshold and set an expiration time on the key.

💡 Why This Matters

🌍 Real World

Counting page visits or user actions in real time is common in web analytics and monitoring.

💼 Career

Understanding Redis counters is useful for backend developers and DevOps engineers managing fast, scalable data stores.

1

DATA SETUP: Create a Redis key called page_visits with initial value 0

Use the Redis command SET page_visits 0 to create a key named page_visits with the value 0.

Redis

# Your Redis command here
# Use SET to create the key page_visits with value 0

Hint

Use the SET command to create a key with a starting value.

2

CONFIGURATION: Define a threshold variable visit_threshold with value 10

Create a Redis key called visit_threshold and set its value to 10 using the SET command.

Redis

SET page_visits 0
# Your Redis command here
# Set visit_threshold to 10

Hint

Use SET visit_threshold 10 to create the threshold key.

3

CORE LOGIC: Increment the page_visits counter using the INCR command

Use the Redis command INCR page_visits to increase the visit count by 1.

Redis

SET page_visits 0
SET visit_threshold 10
# Your Redis command here
# Increment page_visits by 1

Hint

The INCR command increases the integer value of a key by one.

4

COMPLETION: Check if page_visits reached visit_threshold and set expiration of 3600 seconds

Use the Redis command GET page_visits to retrieve the current count, then use GET visit_threshold to get the threshold. Finally, use EXPIRE page_visits 3600 to set the key to expire in one hour.

Redis

SET page_visits 0
SET visit_threshold 10
INCR page_visits
# Your Redis commands here
# Get page_visits and visit_threshold, then set expiration on page_visits

Hint

Use GET to read values and EXPIRE to set a time limit on the key.

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