RDB vs AOF comparison in Redis - Quick Revision & Key Differences

Recall & Review

beginner

What does RDB stand for in Redis?

RDB stands for Redis Database Backup, which is a snapshotting persistence method that saves the dataset to disk at specified intervals.

beginner

What does AOF stand for in Redis?

AOF stands for Append Only File, a persistence method that logs every write operation received by the server, allowing data recovery by replaying these commands.

intermediate

How does RDB persistence affect Redis performance?

RDB saves snapshots at intervals, so it has low overhead during normal operation but can lose recent data if Redis crashes between snapshots.

intermediate

What is a key advantage of AOF over RDB?

AOF provides better durability because it logs every write operation, minimizing data loss by replaying commands after a crash.

intermediate

What is a common downside of using AOF compared to RDB?

AOF files are usually larger and can slow down Redis performance due to frequent disk writes, especially if fsync is set to always.

Which Redis persistence method saves data by creating snapshots at intervals?

A RDB

B AOF

C Both RDB and AOF

D None

RDB saves snapshots of the dataset at specified intervals.

Which persistence method logs every write operation to disk?

A Neither

B RDB

C AOF

D Both

AOF logs every write operation to allow replaying commands for recovery.

What is a main risk when using only RDB persistence?

A File size grows too large

B Data loss between snapshots

C Slower recovery time

D Commands are not logged

RDB can lose data written after the last snapshot if Redis crashes.

Which persistence method generally results in larger disk files?

A RDB

B Neither

C Both are equal

D AOF

AOF files tend to be larger because they log every write operation.

Which persistence method can impact Redis performance more due to frequent disk writes?

A AOF

B RDB

C Neither

D Both equally

AOF can slow performance because it writes every command to disk.

Explain the main differences between RDB and AOF persistence methods in Redis.

Think about how each method saves data and the trade-offs.

Describe a scenario where you might prefer RDB over AOF for Redis persistence.

Consider the balance between speed and data safety.

Practice

1. Which Redis persistence method saves the entire dataset at specific time intervals?

easy

A. AOF (Append Only File)

B. RDB (Redis Database snapshot)

C. Both RDB and AOF save snapshots

D. Neither RDB nor AOF save snapshots

Solution

1. Step 1: Understand RDB persistence

   RDB saves the dataset by creating snapshots at set intervals.

2. Step 2: Compare with AOF

   AOF logs every write operation, not snapshots.

3. Final Answer:

   RDB (Redis Database snapshot) -> Option B

4. Quick Check:

   Snapshot saving = RDB [OK]

Hint: RDB = snapshots at intervals, AOF = logs every change [OK]

Common Mistakes:

• Confusing AOF with snapshot saving
• Thinking both save snapshots
• Believing neither saves snapshots

2. Which of the following is the correct Redis command to enable AOF persistence?

easy

A. CONFIG SET appendonly yes

B. CONFIG SET save "900 1 300 10 60 10000"

C. CONFIG SET rdbcompression no

D. CONFIG SET maxmemory-policy allkeys-lru

Solution

1. Step 1: Identify AOF enabling command

   The command to enable AOF is CONFIG SET appendonly yes.

2. Step 2: Check other options

   CONFIG SET save "900 1 300 10 60 10000" sets RDB save intervals, C disables RDB compression, D sets memory eviction policy.

3. Final Answer:

   CONFIG SET appendonly yes -> Option A

4. Quick Check:

   Enable AOF = appendonly yes [OK]

Hint: Enable AOF with 'appendonly yes' command [OK]

Common Mistakes:

• Confusing RDB save command with AOF
• Using unrelated config commands
• Forgetting to set appendonly to yes

3. Given Redis configured with AOF enabled and fsync set to 'everysec', what is the expected data durability behavior?

medium

A. Data is saved only at intervals, risking data loss of last seconds

B. Every write is immediately saved to disk, no data loss

C. Data is never saved to disk automatically

D. Data is saved only when Redis restarts

Solution

1. Step 1: Understand AOF with fsync everysec

   With fsync set to 'everysec', Redis writes AOF data to disk every second.

2. Step 2: Analyze durability implications

   This means data could be lost if Redis crashes within the last second before fsync.

3. Final Answer:

   Data is saved only at intervals, risking data loss of last seconds -> Option A

4. Quick Check:

   AOF everysec fsync = possible 1-second data loss [OK]

Hint: AOF everysec fsync means possible 1-second data loss [OK]

Common Mistakes:

• Assuming every write is immediately saved
• Thinking data is never saved automatically
• Confusing with no persistence

4. You enabled both RDB and AOF persistence in Redis, but after a crash, data is missing. What is the most likely cause?

medium

A. Redis does not support using both RDB and AOF together

B. Redis was not restarted after enabling persistence

C. RDB snapshot interval is too long, losing recent changes

D. AOF file is corrupted and Redis cannot load it

Solution

1. Step 1: Understand RDB and AOF coexistence

   Redis supports both RDB and AOF, preferring to load AOF first on restart if available.

2. Step 2: Analyze data loss causes

   With both enabled, if data is missing after a crash, the most likely cause is AOF corruption, causing fallback to the older RDB snapshot and loss of recent changes.

3. Final Answer:

   AOF file is corrupted and Redis cannot load it -> Option D

4. Quick Check:

   Data loss with both = AOF corrupted [OK]

Hint: With both enabled, data loss likely from AOF corruption [OK]

Common Mistakes:

• Believing Redis can't use both persistences
• Thinking RDB interval too long is the cause
• Forgetting to restart Redis

5. You want Redis to recover data quickly after a crash but can tolerate losing up to 1 minute of recent writes. Which persistence setup is best?

hard

A. Enable AOF with fsync always, disable RDB

B. Enable both RDB and AOF with fsync everysec

C. Enable RDB snapshots every 60 seconds, disable AOF

D. Disable both RDB and AOF for fastest performance

Solution

1. Step 1: Match recovery speed and data loss tolerance

   RDB snapshots every 60 seconds allow fast recovery but may lose up to 1 minute of data.

2. Step 2: Compare with AOF options

   AOF with fsync always is slower but safer; both enabled adds overhead; disabling persistence risks total data loss.

3. Final Answer:

   Enable RDB snapshots every 60 seconds, disable AOF -> Option C

4. Quick Check:

   Fast recovery + 1 min loss = RDB every 60s [OK]

Hint: RDB snapshots match fast recovery with some data loss [OK]

Common Mistakes:

• Choosing AOF for fast recovery despite slower startup
• Enabling both causing unnecessary overhead
• Disabling persistence risking total data loss