Transaction Control (ACID) - Foundation for understanding isolation

Locking Mechanisms - Row-level locks, table-level locks, range locks

Deadlock Detection - Wait-for graphs, deadlock prevention strategies

MVCC (Multi-Version Concurrency Control) - PostgreSQL implementation

Optimistic Locking - Check version before update, no locks during read

Pessimistic Locking - Acquire locks before read, hold until commit

Concurrency Control - Timestamp ordering, validation-based protocols

Test dirty reads with Read Uncommitted vs Read Committed

Reproduce non-repeatable reads with Read Committed vs Repeatable Read

Demonstrate phantom reads with Repeatable Read vs Serializable

Implement financial report with Repeatable Read for consistent snapshot

Build seat booking system with Serializable to prevent overbooking

Compare performance: Read Committed vs Serializable (measure TPS)

Handle serialization failures with retry logic and exponential backoff

Design isolation level strategy for e-commerce application

Explain four isolation levels and when to use each

What are dirty reads, non-repeatable reads, phantom reads?

Compare PostgreSQL, MySQL, SQL Server isolation implementations

Why is Read Committed default in most databases?

When would you use Serializable? What are the trade-offs?

How does PostgreSQL Serializable Snapshot Isolation (SSI) work?

Design isolation strategy for payment processing system

How do you handle serialization failures in Serializable?

PostgreSQL Isolation Levels: https://www.postgresql.org/docs/current/transaction-iso.html

MySQL Isolation Levels: https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-isolation-levels.html

SQL Server Isolation Levels: https://docs.microsoft.com/en-us/sql/t-sql/statements/set-transaction-isolation-level-transact-sql

ANSI SQL-92 Isolation Levels: https://en.wikipedia.org/wiki/Isolation_(database_systems)

Serializable Snapshot Isolation: https://wiki.postgresql.org/wiki/SSI

MVCC Explained: https://www.postgresql.org/docs/current/mvcc.html