In database systems, consistency (or correctness) refers to the requirement that any given database transaction must change affected data only in allowed ways. Any data written to the database must be valid according to all defined rules, including constraints, cascades, triggers, and any combination thereof. This does not guarantee correctness of the transaction in all ways the application programmer might have wanted (that is the responsibility of application-level code) but merely that any programming errors cannot result in the violation of any defined database constraints.[1]
In a distributed system, referencing CAP theorem, consistency can also be understood as after a successful write, update or delete of a Record, any read request immediately receives the latest value of the Record.
As an ACID guarantee
editConsistency is one of the four guarantees that define ACID transactions; however, significant ambiguity exists about the nature of this guarantee. It is defined variously as:
- The guarantee that database constraints are not violated, particularly once a transaction commits.[2][3][4][5][6]
- The guarantee that any transactions started in the future necessarily see the effects of other transactions committed in the past.[7][8]
As these various definitions are not mutually exclusive, it is possible to design a system that guarantees "consistency" in every sense of the word, as most relational database management systems in common use today arguably do.
As a CAP trade-off
editThe CAP theorem is based on three trade-offs, one of which is "atomic consistency" (shortened to "consistency" for the acronym), about which the authors note, "Discussing atomic consistency is somewhat different than talking about an ACID database, as database consistency refers to transactions, while atomic consistency refers only to a property of a single request/response operation sequence. And it has a different meaning than the Atomic in ACID, as it subsumes the database notions of both Atomic and Consistent."[7] In the CAP theorem, you can only have two of the following three properties: consistency, availability, or partition tolerance. Therefore, consistency may have to be traded off in some database systems.
See also
editReferences
edit- ^ C. J. Date, "SQL and Relational Theory: How to Write Accurate SQL Code 2nd edition", O'reilly Media, Inc., 2012, pg. 180.
- ^ Haerder, T; Reuter, A. (December 1983). "Principles of Transaction-Oriented Database Recovery" (PDF). Computing Surveys. 15 (4): 287–317. doi:10.1145/289.291. S2CID 207235758. Archived from the original (PDF) on 2017-09-07.
- ^ Mike Chapple. "The ACID Model". About. Archived from the original on 2016-12-29. Retrieved 2014-07-23.
- ^ "ACID properties".
- ^ Cory Janssen. "What is ACID in Databases? - Definition from Techopedia". Techopedia.com.
- ^ "ISO/IEC 10026-1:1998 - Information technology -- Open Systems Interconnection -- Distributed Transaction Processing -- Part 1: OSI TP Model".
- ^ a b "Brewer's Conjecture and the Feasibility of Consistent, Available, Partition-Tolerant Web Services" (PDF). Archived from the original (PDF) on 2019-06-29.
- ^ Ports, D.R.K.; Clements, A.T.; Zhang, I.; Madden, S.; Liskov, B. "Transactional Consistency and Automatic Management in an Application Data Cache" (PDF). Mit Csail.