Why XADD for adding entries in Redis? - Purpose & Use Cases

The Big Idea

What if you could never lose track of your important events again?

The Scenario

Imagine you have a notebook where you write down every event happening in your shop, like sales or deliveries. You try to keep it organized by writing each event on a new page manually.

The Problem

Writing events manually is slow and easy to mess up. You might forget to write the time, mix up the order, or lose track of important details. It becomes hard to find specific events later.

The Solution

XADD in Redis automatically adds new events to a stream with a unique ID and timestamp. It keeps everything in order and easy to find, so you never lose track of your data.

Before vs After

✗ Before

Write event details on paper with date and time by hand

✓ After

XADD mystream * event "sale" amount "100"

What It Enables

With XADD, you can quickly and reliably record events in order, enabling real-time tracking and easy data retrieval.

Real Life Example

A delivery company uses XADD to log every package scanned at different checkpoints, ensuring accurate tracking and timely updates.

Key Takeaways

Manual event recording is slow and error-prone.

XADD automates adding ordered entries with unique IDs.

This makes event tracking reliable and easy to manage.

Practice

1. What does the Redis command XADD do?

easy

A. Adds a new entry to a Redis stream with a unique ID

B. Deletes an entry from a Redis stream

C. Reads entries from a Redis stream

D. Creates a new Redis database

Solution

1. Step 1: Understand the purpose of XADD

   XADD is used to add new entries to a Redis stream, each with a unique ID generated by Redis or specified by the user.

2. Step 2: Compare with other commands

   Deleting entries is done by XDEL, reading by XRANGE or XREAD, and creating databases is unrelated to XADD.

3. Final Answer:

   Adds a new entry to a Redis stream with a unique ID -> Option A

4. Quick Check:

   XADD adds entries = A [OK]

Hint: XADD always adds entries to streams, not deletes or reads [OK]

Common Mistakes:

• Confusing XADD with XDEL or XRANGE
• Thinking XADD creates databases
• Assuming XADD reads data instead of adding

2. Which of the following is the correct syntax to add an entry with fields name and age to a Redis stream mystream using XADD?

easy

A. XADD mystream name John age 30 *

B. XADD mystream name=John age=30 *

C. XADD mystream * name John age 30

D. XADD mystream * (name John) (age 30)

Solution

1. Step 1: Recall XADD syntax

   The correct syntax is: XADD stream_name * field1 value1 field2 value2 ... The asterisk (*) tells Redis to generate the ID automatically.

2. Step 2: Check each option

   XADD mystream * name John age 30 matches the syntax exactly. Options A, C, and D have incorrect order or formatting.

3. Final Answer:

   XADD mystream * name John age 30 -> Option C

4. Quick Check:

   XADD syntax = XADD stream * fields [OK]

Hint: Use * right after stream name to auto-generate ID [OK]

Common Mistakes:

• Placing * after fields instead of immediately after stream name
• Using equal signs (=) in field-value pairs
• Adding parentheses around fields

3. Given the Redis command: XADD mystream MAXLEN 2 * temperature 22 humidity 60 executed three times in a row, how many entries will mystream contain afterwards?

medium

A. 2 entries

B. 0 entries

C. 1 entry

D. 3 entries

Solution

1. Step 1: Understand MAXLEN usage

   The MAXLEN 2 option limits the stream length to 2 entries by trimming older entries when new ones are added.

2. Step 2: Apply the command three times

   After the first two adds, the stream has 2 entries. The third add triggers trimming, keeping only the latest 2 entries.

3. Final Answer:

   2 entries -> Option A

4. Quick Check:

   MAXLEN 2 limits stream to 2 entries [OK]

Hint: MAXLEN limits entries; stream never exceeds that number [OK]

Common Mistakes:

• Assuming all 3 entries remain without trimming
• Confusing MAXLEN with deleting all entries
• Thinking MAXLEN sets minimum length

4. What is wrong with this command? XADD mystream MAXLEN 5 name John age

medium

A. Stream name cannot be 'mystream'

B. MAXLEN must be after the fields

C. XADD does not support MAXLEN option

D. Missing value for field 'age'

Solution

1. Step 1: Check field-value pairs

   Fields and values must come in pairs. Here, 'age' has no value following it.

2. Step 2: Verify MAXLEN position and support

   MAXLEN is correctly placed after stream name and before fields. XADD supports MAXLEN.

3. Final Answer:

   Missing value for field 'age' -> Option D

4. Quick Check:

   Fields need values; 'age' missing one [OK]

Hint: Every field must have a value; check pairs carefully [OK]

Common Mistakes:

• Forgetting to provide value for last field
• Misplacing MAXLEN option
• Thinking stream name is invalid

5. You want to add multiple entries to a Redis stream sensor_data but keep only the latest 100 entries to save memory. Which command correctly adds a new entry with fields temp and humidity and enforces this limit?

hard

A. XADD sensor_data * MAXLEN 100 temp 25 humidity 40

B. XADD sensor_data MAXLEN 100 * temp 25 humidity 40

C. XADD sensor_data MAXLEN ~ 100 * temp 25 humidity 40

D. XADD sensor_data * temp 25 humidity 40 MAXLEN 100

Solution

1. Step 1: Understand MAXLEN usage and placement

   MAXLEN must come immediately after the stream name, optionally with ~ for approximate trimming. The * must come after MAXLEN to auto-generate ID.

2. Step 2: Analyze options

   XADD sensor_data MAXLEN 100 * temp 25 humidity 40 correctly places MAXLEN 100 after stream name and before *, then fields. XADD sensor_data MAXLEN ~ 100 * temp 25 humidity 40 uses ~ (approximate) which is optional but not required. Options B and D have wrong order.

3. Final Answer:

   XADD sensor_data MAXLEN 100 * temp 25 humidity 40 -> Option B

4. Quick Check:

   MAXLEN 100 before * enforces limit [OK]

Hint: Put MAXLEN right after stream name, then * for ID [OK]

Common Mistakes:

• Placing MAXLEN after * or fields
• Using ~ when exact trimming is needed
• Adding MAXLEN at the end of command