An interactive concept flow for transactions, isolation, and mvcc snapshots, from its assumptions through the main operation and boundary checks.
trace / request.md
readyA transaction groups operations under a database contract such as atomicity and consistency. Multi-version concurrency control keeps versions of rows so readers can observe a consistent snapshot while writers create new versions. The exact snapshot and conflict rules depend on the database and isolation level.
Use the stages in order to explain transactions, isolation, and mvcc snapshots. Each stage makes one assumption visible: what the operation promises, what representation it uses, how state changes, which boundary can invalidate a shortcut, and what evidence confirms the result.
For a worked explanation, continue to the topic article and execution trace.
Not started
Sign in to save your learning progress.