Timestamp Concurrency Control: No Locks, Just Time
Timestamp-based concurrency control bets that transaction conflicts are rare, using timestamps to order operations instead of locking data. It's used where lock overhead is high, but the footgun is that frequent conflicts can cause transaction starvation.
Timestamp-based concurrency control is an optimistic method that bets transaction conflicts are rare. Instead of using locks, it assigns a unique timestamp to each transaction and validates their order. This is for systems where lock contention is a bottleneck and rollbacks are acceptable. The footgun is that in high-contention workloads, it can lead to repeated transaction aborts and starvation for long-running transactions that constantly conflict with newer ones.
Read the original → Wikipedia: Timestamp-based concurrency control
- #database
- #concurrency
- #transactions
- #optimistic locking
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.