Lesson plan

Acid

In database systems, ACID is an acronym for atomicity, consistency, isolation, and durability: four properties used to characterize reliable database transactions. Together, the properties describe how a transaction behaves with respect to failure, database invariants, concurrent execution, and persistence after commit. A common example is a transfer of money between two bank accounts. The debit and credit can be treated as one transaction: atomicity requires the transfer to take effect as a whole or not at all; consistency requires the transaction to preserve defined database invariants; isolation governs its interaction with concurrent transactions; and durability requires a successfully committed transfer to survive subsequent failures. The acronym ACID appears in Theo Härder and Andreas Reuter's influential 1983 paper Principles of Transaction-Oriented Database Recovery, which built on earlier work on transaction processing by researchers including Jim Gray.

Back to article

Article summary

In database systems, ACID is an acronym for atomicity, consistency, isolation, and durability: four properties used to characterize reliable database transactions. Together, the properties describe how a transaction behaves with respect to failure, database invariants, concurrent execution, and persistence after commit. A common example is a transfer of money between two bank accounts. The debit and credit can be treated as one transaction: atomicity requires the transfer to take effect as a whole or not at all; consistency requires the transaction to preserve defined database invariants; isolation governs its interaction with concurrent transactions; and durability requires a successfully committed transfer to survive subsequent failures. The acronym ACID appears in Theo Härder and Andreas Reuter's influential 1983 paper Principles of Transaction-Oriented Database Recovery, which built on earlier work on transaction processing by researchers including Jim Gray.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.