Why Two-phase locking (2PL) in DBMS Theory? - Purpose & Use Cases

The Big Idea

What if your bank account balance got messed up because two people changed it at once?

The Scenario

Imagine multiple people trying to edit the same document at the same time without any rules. They overwrite each other's changes, causing confusion and mistakes.

The Problem

Without a system to control access, changes can clash, data can become inconsistent, and it's hard to know which version is correct. This leads to errors and lost work.

The Solution

Two-phase locking (2PL) sets clear rules for when to lock and unlock data during transactions. It ensures that no two people change the same data at once, keeping everything safe and consistent.

Before vs After

✗ Before

start transaction
update data
commit
// no locks, possible conflicts

✓ After

start transaction
acquire locks
update data
commit
release locks
// safe and consistent

What It Enables

It enables multiple users to work on the database simultaneously without causing errors or losing data.

Real Life Example

In a bank, two tellers updating the same account balance at the same time use 2PL to avoid mistakes like withdrawing more money than available.

Key Takeaways

2PL controls when data is locked and unlocked during transactions.

This prevents conflicts and keeps data consistent.

It allows safe multi-user access to databases.