Database replication
By: Bettina Kemme, Ricardo Jiménez Peris, Marta Patiño-Martínez
Contributors: Jiménez-Peris, R. (Ricardo); Patiño-Martínez, M. (Marta)
Series: Synthesis lectures on data management -- # 7
Publisher: Morgan & Claypool; Morgan & Claypool Publishers
Published: 2010
Place of publication: San Rafael, Calif. (1537 Fourth Street, San Rafael, CA 94901 USA)
Language: eng
Format: [electronic resource] /
Number of pages: 141
ISBN-13: 9781608453825; 9781608453818
Subjects: Distributed databases
Other titles: Synthesis digital library of engineering and computer science.
Description: Database replication is widely used for fault-tolerance, scalability and performance. The failure of one database replica does not stop the system from working as available replicas can take over the tasks of the failed replica. Scalability can be achieved by distributing the load across all replicas, and adding new replicas should the load increase. Finally, database replication can provide fast local access, even if clients are geographically distributed clients, if data copies are located close to clients.
Notes: Part of: Synthesis digital library of engineering and computer science.

Series from website.

Includes bibliographical references (p. 129-138).

Abstract freely available; full-text restricted to subscribers or individual document purchasers.

Also available in print.

Mode of access: World Wide Web.

System requirements: Adobe Acrobat Reader.
Table of contents: title: 1. Overview; title: Motivation; title: Challenges; title: Replica control; title: Other issues; title: 2. 1-copy-equivalence and consistency; title: Replication model; title: 1-copy-isolation; title: 1-copy-atomicity; title: 1-copy-durability; title: Relationship between isolation, atomicity and durability; title: 1-copy-consistency; title: Session consistency; title: Eventual consistency; title: 3. Basic protocols; title: Eager protocols; title: Protocol description; title: Example execution; title: Eager properties; title: Primary copy vs. update anywhere; title: Lazy protocols; title: Protocol description; title: Example execution; title: Lazy vs. eager properties; title: Primary copy vs. update anywhere; title: Summary; title: 4. Replication architecture; title: Where to locate the replication logic; title: Kernel based architecture; title: Middleware based architecture; title: Kernel vs. middleware based replication; title: Black vs. grey box middleware; title: Processing of write operations; title: Partial replication; title: Other issues; title: Group communication as building block; title: Group communication and reliable multicast; title: Simplifying replication with group communication; title: Related work; title: 5. The scalability of replication; title: Model; title: The analysis; title: Related work; title: 6. Eager replication and 1-copy-serializability; title: Centralized middleware; title: Protocol; title: Example execution; title: Algorithm properties; title: Discussion; title: Decentralized middleware; title: Protocol; title: Example execution; title: Algorithm properties; title: Discussion; title: Decentralized middleware with asymmetric processing; title: Protocol; title: Example execution; title: Algorithm properties; title: Related work; title: 7. 1-copy-snapshot isolation; title: 1-copy-snapshot isolation; title: Snapshot isolation in a non-replicated system; title: Snapshot isolation in a replicated system; title: Primary copy, centralized middleware; title: Protocol; title: Example execution; title: Algorithm properties; title: Update anywhere, centralized middleware; title: Protocol; title: Example execution; title: Algorithm properties; title: Update-anywhere, decentralized middleware; title: Protocol description; title: Example execution; title: Algorithm properties; title: Snapshot isolation vs.traditional optimistic concurrency control; title: Related work; title: 8. Lazy replication; title: Bounding the staleness in lazy primary copy; title: Boundary types; title: Basic implementation; title: Push vs. pull based refresh; title: Materialized views; title: Transaction propagation; title: Multiple primaries; title: Lazy update anywhere; title: Distributed vs. central conflict management; title: Conflict detection; title: Conflict resolution; title: Related work; title: Bounding staleness; title: Replica placement; title: Conflict detection and resolution; title: 9. Self-configuration and elasticity; title: Self-healing; title: Fault-tolerant measures during normal processing; title: Failure types; title: Failover: client side; title: Failover: server side; title: Recovery; title: Self-optimization; title: Load-balancing; title: Other optimization techniques; title: Elasticity: self-provisioning; title: System reconfiguration; title: Deciding on the right number of replicas; title: Related work; title: 10. Other aspects of replication; title: Multi-tier architectures; title: Quorums; title: Mobile and peer-to-peer environments; title: A. Transactions and the ACID properties; title: A.1. Atomicity; title: A.2. Consistency; title: A.3. Durability; title: A.4. Isolation; title: A.5. Distributed transactions and 2-phase commit; title: Bibliography; title: Authors' biographies.