Why Combined RDB + AOF in Redis? - Purpose & Use Cases

The Big Idea

What if your data vanished just because you waited too long to save it?

The Scenario

Imagine you run a busy store and keep track of sales on paper. Every hour, you copy all sales into a big book. But if the store closes suddenly, you lose all sales since the last copy.

The Problem

Copying all sales manually every hour is slow and misses recent sales if a sudden event happens. Also, writing every sale on paper takes time and can cause mistakes or lost data.

The Solution

Combined RDB + AOF in Redis saves a full snapshot occasionally (RDB) and logs every change (AOF). This way, you get fast recovery from snapshots and no lost data from recent changes.

Before vs After

✗ Before

save_every_hour()
log_changes_manually()

✓ After

redis.conf: save snapshots + appendonly yes

What It Enables

You can recover your data quickly and safely without losing recent updates, even if the system crashes unexpectedly.

Real Life Example

An online game saves player scores every few minutes (RDB) and records every move instantly (AOF), so no progress is lost if the server restarts.

Key Takeaways

Manual backups miss recent changes and are slow.

RDB snapshots save full data fast but can lose recent updates.

AOF logs every change to prevent data loss.