Why WATCH for optimistic locking in Redis? - Purpose & Use Cases

The Big Idea

What if your data could protect itself from accidental overwrites by others?

The Scenario

Imagine two friends trying to update the same shopping list on paper at the same time. They both write changes without knowing what the other wrote, causing confusion and mistakes.

The Problem

Manually checking and updating shared data can be slow and error-prone. Without a way to detect changes made by others, updates can overwrite each other, leading to lost or incorrect information.

The Solution

WATCH in Redis helps by "watching" keys for changes before making updates. If someone else changes the data first, your update is stopped, preventing conflicts and keeping data safe.

Before vs After

✗ Before

GET key
// modify value
SET key new_value

✓ After

WATCH key
MULTI
SET key new_value
EXEC

What It Enables

This lets multiple users safely update shared data without accidentally overwriting each other's changes.

Real Life Example

In a multiplayer game, players update their scores at the same time. WATCH ensures each score update is correct and no points are lost.

Key Takeaways

Manual updates can cause data conflicts.

WATCH detects changes before updating.

It keeps shared data safe and consistent.