Three-phase commit protocol
In computer networking and distributed databases, the three-phase commit protocol (3PC) is a distributed algorithm that ensures all nodes in a system agree to commit or abort a transaction. It improves upon the two-phase commit protocol (2PC) by eliminating the possibility of indefinite blocking caused by a specific type of failure during the commit phase.
From Wikipedia, the free encyclopedia In computer networking and distributed databases, the three-phase commit protocol (3PC)[1] is a distributed algorithm that ensures all nodes in a system agree to commit or abort a transaction. It improves upon the two-phase commit protocol (2PC) by eliminating the possibility of indefinite blocking caused by a specific type of failure during the commit phase. A two-phase commit protocol cannot dependably recover from a failure of both the coordinator and a cohort member during the commit phase. If only the coordinator had failed, and no cohort members…
saved by
related reading
- DBMS Musings: It’s Time to Move on from Two Phase Commitdbmsmusings.blogspot.com
- 67.4. Two-Phase Transactionspostgresql.org
- Distributed Transactions - Database Systemscs186berkeley.net
- Secure multi-party computation - Wikipediaen.wikipedia.org
- Let’s take a crack at understanding distributed consensuspreethikasireddy.com
- What is the difference between PBFT, Tendermint, HotStuff, and HotStuff-2?decentralizedthoughts.github.io
- Upgrading Ethereum | 2.3.4 Casper FFGeth2book.info
- Protocol in a Nutshell | Simplex Consensussimplex.blog
- Multimmit: Extending Blocks for Faster Finalityarxiv.org
- Chain Replication for Supporting High Throughput and Availabilitycs.cornell.edu
- practical Byzantine Fault Tolerance(pBFT) - GeeksforGeeksgeeksforgeeks.org
- Scaling Replicated State Machines with Compartmentalizationmwhittaker.github.io