Encyclopedia of Database Systems

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

Concurrency Control for Replicated Databases

  • Bettina KemmeEmail author
Reference work entry
DOI: https://doi.org/10.1007/978-1-4614-8265-9_433


Isolation in Replicated Databases


Data replication is a core technology to achieve fault tolerance, high availability, and increased performance. Each “logical” data item has one or more physical data copies, also called replicas, that are distributed across the database servers in the system. Replica controlis the task of translating the read and write operations on logical data items into operations on the physical data copies. When data is accessed with transactional context, replica control has to be combined with concurrency control in order to provide global isolation of concurrent transactions across the entire system. Just as centralized database systems, replicated database systems offer several levels of isolation and replica consistency. One-copy serializability was developed as a first – and very strong – correctness criterion requiring that the concurrent execution of transactions in a replicated system is equivalent to a serial execution of these...

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

Recommended Reading

  1. 1.
    Abbadi AEl, Toueg S. Availability in partitioned replicated databases. In: Proceedings of the 5th ACM SIGACT-SIGMOD Symposium on Principles of Database Systems; 1986. p. 240–51.Google Scholar
  2. 2.
    Bernstein PA, Goodman N. An algorithm for concurrency control and recovery in replicated distributed databases. ACM Trans Database Syst. 1984;9(4):596–615.MathSciNetCrossRefGoogle Scholar
  3. 3.
    Bernstein PA, Hadzilacos V, Goodman N. Concurrency control and recovery in database systems. Reading: Addison Wesley; 1987.Google Scholar
  4. 4.
    Carey MJ, Livny M. Conflict detection tradeoffs for replicated data. ACM Trans Database Syst. 1991;16(4):703–46.CrossRefGoogle Scholar
  5. 5.
    Gray J, Helland P, O’Neil P, Shasha D. The dangers of replication and a solution. In: Proceedings of the ACM SIGMOD International Conference on Management of Data; 1996. p. 173–82.Google Scholar
  6. 6.
    Kemme B, Alonso G. A suite of database replication protocols based on group communication primitives. In: Proceedings of the 18th IEEE International Conference on Distributed Computing Systems; 1998. p. 156–63.Google Scholar
  7. 7.
    Kindberg T, Coulouris GF, Dollimore J. Distributed systems: concepts and design. 4th ed. Harlow/New York: Addison Wesley; 2005.zbMATHGoogle Scholar
  8. 8.
    Kung HT, Robinson JT. On optimistic methods for concurrency control. ACM Trans Database Syst. 1981;6(2):213–26.CrossRefGoogle Scholar
  9. 9.
    Lamport L. The part-time parliament. ACM Trans Comput Syst. 1998;16(2):133–69.CrossRefGoogle Scholar
  10. 10.
    Lin Y, Kemme B, Jiménez-Peris R, Patiño-Martínez M, Armendáriz-Iñigo JE. Snapshot isolation and integrity constraints in replicated databases. ACM Trans Database Syst. 2009;34(2):Article 11.CrossRefGoogle Scholar
  11. 11.
    Pedone F, Guerraoui R, Schiper A. The database state machine approach. Distrib Parallel Databases. 2003;14(1):71–98.CrossRefGoogle Scholar
  12. 12.
    Sovran Y, Power R, Aguilera MK, Li J. Transactional storage for geo-replicated systems. In: Proceedings of the 23rd ACM Symposium on Operating System Principles; 2011. p. 385–400.Google Scholar

Copyright information

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

Authors and Affiliations

  1. 1.School of Computer ScienceMcGill UniversityMontrealCanada