Topic
Transactions
Learn Transactions as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts13 Articles6h 28m
Overview
Learn Transactions as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
Databases
Distributed Systems
Isolation Levels
Acid
Learning Path in this Topic
Series that contain articles from Transactions. Select a path to filter the article list.
Articles
13 matched articles
Article 1Dirty Read Explained: How Uncommitted Data Corrupts TransactionsTLDR: A dirty read occurs when Transaction B reads data written by Transaction A before A has committed. If A rolls back, B has made decisions on data that — from the database's perspective — never ex30 min
Article 2ACID Transactions in Distributed Databases: DynamoDB, Cosmos DB, and Spanner ComparedTLDR: ACID transactions in distributed databases are not equal. DynamoDB provides multi-item atomicity scoped to 25 items using two-phase commit with a coordinator item, but only within a single regio39 minArticle 3Distributed Transactions: 2PC, Saga, and XA ExplainedTLDR: Distributed transactions require you to choose a consistency model before choosing a protocol. 2PC and XA give atomic all-or-nothing commits but block all participants on coordinator failure. Sa26 min
Article 4ACID Properties Explained: How SQL Databases Guarantee Atomicity, Consistency, Isolation, and DurabilityTLDR: ACID is four orthogonal guarantees that every SQL transaction must provide. Atomicity says all-or-nothing: PostgreSQL implements it via WAL rollback; MySQL InnoDB via undo logs. Consistency says38 min
Article 5Dirty Write Explained: When Uncommitted Data Gets OverwrittenTLDR: A dirty write occurs when Transaction B overwrites data that Transaction A has written but not yet committed. The result is not a rollback or an error — it is silently inconsistent committed dat28 min
Article 6Read Skew Explained: Inconsistent Snapshots Across Multiple ObjectsTLDR: Read skew occurs when a transaction reads two logically related objects at different points in time — one before and one after a concurrent transaction commits — producing a view that never exis34 minPage 1 of 3