Distributed Transactions: 2PC Principles and Replication Strategies

This lecture covers the principles of the Two-Phase Commit (2PC) protocol, detailing the process of prepare, vote, commit/abort, and acknowledgment messages. It also discusses scenarios like coordinator and subordinate failures, site and link failures, and the use of presumed commit/abort. Additionally, it explores replication strategies such as synchronous and asynchronous replication, primary site replication, and peer-to-peer replication. The lecture delves into the CAP theorem, consistency, availability, and partition tolerance, as well as the transition from ACID to BASE properties in NoSQL systems.

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Related lectures (33)

Related concepts (39)

CS-422: Database systems

This course is intended for students who want to understand modern large-scale data analysis systems and database systems. It covers a wide range of topics and technologies, and will prepare students

MySQL Cluster

MySQL Cluster is a technology providing shared-nothing clustering and auto-sharding for the MySQL database management system. It is designed to provide high availability and high throughput with low latency, while allowing for near linear scalability. MySQL Cluster is implemented through the NDB or NDBCLUSTER storage engine for MySQL ("NDB" stands for Network Database). MySQL Cluster is designed around a distributed, multi-master ACID compliant architecture with no single point of failure.

Replication (computing)

Replication in computing involves sharing information so as to ensure consistency between redundant resources, such as software or hardware components, to improve reliability, fault-tolerance, or accessibility. Replication in computing can refer to: Data replication, where the same data is stored on multiple storage devices Computation replication, where the same computing task is executed many times.

Two-phase commit protocol

In transaction processing, databases, and computer networking, the two-phase commit protocol (2PC, tupac) is a type of atomic commitment protocol (ACP). It is a distributed algorithm that coordinates all the processes that participate in a distributed atomic transaction on whether to commit or abort (roll back) the transaction. This protocol (a specialised type of consensus protocol) achieves its goal even in many cases of temporary system failure (involving either process, network node, communication, etc.

Multi-master replication

Multi-master replication is a method of database replication which allows data to be stored by a group of computers, and updated by any member of the group. All members are responsive to client data queries. The multi-master replication system is responsible for propagating the data modifications made by each member to the rest of the group and resolving any conflicts that might arise between concurrent changes made by different members.

Atomic commit

In the field of computer science, an atomic commit is an operation that applies a set of distinct changes as a single operation. If the changes are applied, then the atomic commit is said to have succeeded. If there is a failure before the atomic commit can be completed, then all of the changes completed in the atomic commit are reversed. This ensures that the system is always left in a consistent state. The other key property of isolation comes from their nature as atomic operations.

Distributed Transactions: Replication Strategies CS-422: Database systems

Explores replication strategies for fault tolerance, load balancing, and eventual consistency in distributed transactions.

Parallel Databases CS-322: Introduction to database systems

Explores parallel and distributed databases, covering architectures, query optimization, data storage, and distributed transactions.

Gitlab Agent for Kubernetes (`agentk`)

Covers the setup of a Gitlab agent for Kubernetes, focusing on installation, version control, and troubleshooting.

Transactions and Concurrency Control CS-422: Database systems

Delves into lock-based concurrency control, deadlock handling, transaction models, and their limitations.

Eventual Consistency: NoSQL, CAP Theorem, and BASE CS-422: Database systems

Explores NoSQL databases, CAP theorem, BASE principles, and eventual consistency in distributed systems.