tldr: Concurrency Control & Recovery
Part of the tldr series , which summarizes papers I'm currently reading. Inspired by the morning paper . tldr: Concurrency Control & Recovery Franklin Concurrency control makes sure that users see consistent states of the database even though users' operations may be concurrent. Recovery makes sure that software or hardware failures don't corrupt the database state. Together, these DBMS components make things easier for developers who create applications on top of a database. Transactions A transaction groups a set of logical operations into a unit, that all abort or all commit as one. If a transaction commits , all its updates become permanent and visible to other transactions. If a transaction aborts , all its updates are erased. The properties that a transaction should have are: A tomicity: all or none of the operations in a transaction succeed. C onsistency: the transaction leaves the database in a consistent * state. *A circular definition, bu