Part 1 of 6 · 1 min read
Why this page opens the level
In this module you will
- Define a transaction and say what problem it solves.
- Explain each letter of ACID in plain words, including why the C is different from the others.
- Tell single-object operations from multi-object transactions, with an example of each need.
- Say why durability is a matter of risk reduction and not a guarantee.
- Retry an aborted transaction safely, and name five ways a retry can go wrong.
Levels 2 to 4 stored and copied data. This level asks what the data store promises when many clients write at once and machines fail. Transactions are the oldest and most important of those promises. Every later page (isolation, consensus, distributed transactions) refines or relaxes what is defined here. The tier is Core. The numbers are made up to show the idea, unless the text names a book.