Encyclopedia of Database Systems

2018 Edition
| Editors: Ling Liu, M. Tamer Özsu

Transaction Models: The Read/Write Approach

  • Gottfried Vossen
Reference work entry
DOI: https://doi.org/10.1007/978-1-4614-8265-9_435

Synonyms

Page model; Read/write model; Transaction model

Definition

The transaction concept essentially establishes an “ACID contract” in data-processing situations, and a transaction model is an abstraction concept that makes this concept amenable to realizations. Two fundamental models are the page model as well as the object model, where the former is an execution model and the latter is more a conceptual model. The page model is based on the perception that database operations ultimately are read or write operations on pages that need to be transferred between secondary storage and main memory or the database buffer. The model allows making all relevant notions (in particular interleavings of multiple transactions and schedule correctness) precise in a syntactic manner, and it forms the basis for verifying a variety of concurrency control algorithms that can be used in database management as well as other systems.

Historical Background

The read/write or page model of transactions...

This is a preview of subscription content, log in to check access.

Recommended Reading

  1. 1.
    Alonso G, Vingralek R, Agrawal D, Breitbart Y, El Abbadi A, Schek H-J, Weikum G. Unifying concurrency control and recovery of transactions. Inform Syst. 1994;19(1):101–15.CrossRefGoogle Scholar
  2. 2.
    Bernstein PA, Shipman DW, Wong WS. Formal aspects of serializability in database concurrency control. IEEE Trans Software Eng. 1979;SE-5(3):203–16.MathSciNetzbMATHCrossRefGoogle Scholar
  3. 3.
    Bernstein PA, Hadzilacos V, Goodman N. Concurrency control and recovery in database systems. Reading: Addison-Wesley; 1987.Google Scholar
  4. 4.
    Eswaran KP, Gray J, Lorie RA, Traiger IL. The notions of consistency and predicate locks in a database system. Commun ACM. 1976;19(11):624–33.MathSciNetzbMATHCrossRefGoogle Scholar
  5. 5.
    Gray J. Notes on database operating systems. In: Bayer R, Graham MR, Seegmüller G, editors. Operating systems: an advanced course, LNCS, vol. 60. Berlin: Springer; 1978. p. 393–481.CrossRefGoogle Scholar
  6. 6.
    Gray J. The transaction concept: virtues and limitations. In: Proceedings of the 7th International Conference on Very Data Bases; 1981. p. 144–54.Google Scholar
  7. 7.
    Gray J, Reuter A. Transaction processing: concepts and techniques. San Francisco: Morgan Kaufmann; 1993.zbMATHGoogle Scholar
  8. 8.
    Lampson BW. Atomic transactions. In: Lampson BW, Paul M, Siegert HJ, editors. Distributed systems – architecture and implementation: an advanced course, LNCS, vol. 105. Berlin: Springer; 1981. p. 246–85.CrossRefGoogle Scholar
  9. 9.
    Lomet DB. Process structuring, synchronization, and recovery using atomic actions. ACM SIGPLAN Not. 1977;12(3):128–37.MathSciNetCrossRefGoogle Scholar
  10. 10.
    Papadimitriou CH. The serializability of concurrent database updates. J ACM. 1979;26(4):631–53.MathSciNetzbMATHCrossRefGoogle Scholar
  11. 11.
    Papadimitriou CH. The theory of database concurrency control. Rockville: Computer Science; 1986.zbMATHGoogle Scholar
  12. 12.
    Shasha D, Bonnet P. Database tuning – principles, experiments, and troubleshooting techniques. San Francisco: Morgan Kaufmann; 2003.Google Scholar
  13. 13.
    Weikum G, Vossen G. Transactional information systems – theory, algorithms, and the practice of concurrency control and recovery. San Francisco: Morgan Kaufmann; 2002.Google Scholar

Copyright information

© Springer Science+Business Media, LLC, part of Springer Nature 2018

Authors and Affiliations

  1. 1.Department of Information SystemsWestfälische Wilhelms-UniversitätMünsterGermany

Section editors and affiliations

  • Gottfried Vossen
    • 1
  1. 1.Dep. of Inf. SystemsWestfälische Wilhelms-UniversitätMünsterGermany