two-phase commit

(redirected from Two-phase commit protocol)
Also found in: Wikipedia.

two-phase commit

(database)
A technique for maintaining integrity in distributed databases. Where a system uses two or more database, a transaction among the distibuted database should be atomic ("all or nothing"). This is done by handling the transaction in two phases. First the databases prepare the transaction, confirm that it is possible to process it, and lock the relevant record.

Once all the required databases confirm that the transaction is viable, the system instructs them all to commit it - i.e. to make it permanent. If it is not possible to process it, the system will instruct the databases to rollback (undo) the transaction.
This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)

two-phase commit

A technique for ensuring that a transaction successfully updates all appropriate files in a distributed database environment. All DBMSs involved in the transaction first confirm that the transaction has been received and is recoverable (stored on disk). Then each DBMS is told to commit the transaction (do the actual updating).

Traditionally, two-phase-commit meant updating databases in two or more servers, but the term is also applied to updating two or more different databases within the same server. See transaction, transaction file and transaction processing.
Copyright © 1981-2019 by The Computer Language Company Inc. All Rights reserved. THIS DEFINITION IS FOR PERSONAL USE ONLY. All other reproduction is strictly prohibited without permission from the publisher.
References in periodicals archive ?
He explains generally applicable design patterns in MongoDB, including the kinds of documents that can be stored in it, the trade-offs between schemas that embed related documents within related documents and schemas where documents reference one another by ID, the performance benefits of embedding, and when its complexity outweighs the performance gains; how MongoDB collections are schemaless and how this enables a flexible and efficient polymorphism; and how its modifiers can accomplish in a single document update what several updates would do in SQL, as well as a pattern for implementing an application-level, two-phase commit protocol to provide transactional guarantees.
It offers a review of distributed computing fundamentals, an overview of the Jini architecture, and an introduction to the key concepts that are the source of the technology's simplicity and power: remote objects, leasing, distributed events, and a two-phase commit protocol. The formal specification provides the definitive description of every element of the Jini architecture.
For example, it is all but straightforward to extend the transactional service and provide an alternative commitment protocol to the two-phase commit protocol provided by default.
The message queuing subsystem provides additional reliability by maintaining a copy of the agent to be transmitted in an on-disk queue until the recipient of this agent transmission acknowledges receipt via the two-phase commit protocol.
SET features support for two-phase commit protocols, such as those in the XA, Microsoft and BEA execution environments and supports IBM's OS/390 Recoverable Resource Management Services.