Transactions and consistency in distributed database systems

  • Authors:
  • Irving L. Traiger;Jim Gray;Cesare A. Galtieri;Bruce G. Lindsay

  • Affiliations:
  • IBM Research Lab, San Jose, CA;IBM Research Lab, San Jose, CA;IBM Research Lab, San Jose, CA;IBM Research Lab, San Jose, CA

  • Venue:
  • ACM Transactions on Database Systems (TODS)
  • Year:
  • 1982

Quantified Score

Hi-index 0.03

Visualization

Abstract

The concepts of transaction and of data consistency are defined for a distributed system. The cases of partitioned data, where fragments of a file are stored at multiple nodes, and replicated data, where a file is replicated at several nodes, are discussed. It is argued that the distribution and replication of data should be transparent to the programs which use the data. That is, the programming interface should provide location transparency, replica transparency, concurrency transparency, and failure transparency. Techniques for providing such transparencies are abstracted and discussed.By extending the notions of system schedule and system clock to handle multiple nodes, it is shown that a distributed system can be modeled as a single sequential execution sequence. This model is then used to discuss simple techniques for implementing the various forms of transparency.