Scribd
Upload
42 views10 pages

Adbms Vasu

Uploaded by

samjaiwin2210
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
42 views10 pages

Adbms Vasu

Uploaded by

samjaiwin2210
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Advanced Database Management System

M.Vasuki
I – M.Sc Computer Science
What is a Distributed Transaction?

A distributed transaction is a set of


operations on data that is performed across
two or more data repositories (especially
databases). It is typically coordinated across
separate nodes connected by a network, but
may also span multiple databases on a single
server.
There are two possible outcomes:

1) all operations successfully complete,


2) none of the operations are performed at all due to a
failure somewhere in the system.
In the latter case, if some work was completed prior to
the failure, that work will be reversed to ensure no net
work was done.

This type of operation is in compliance with the


“ACID” (atomicity-consistency-isolation-durability)
principles of databases that ensure data integrity.

ACID is most commonly associated with transactions


on a single database server, but distributed transactions
extend that guarantee across multiple databases.
How Do Distributed Transactions Work?

Distributed transactions have the same processing


completion requirements as regular database
transactions, but they must be managed across
multiple resources, making them more challenging to
implement for database developers.
The multiple resources add more points of failure,
such as the separate software systems that run the
resources (e.g., the database software), the extra
hardware servers, and network failures. This makes
distributed transactions susceptible to failures, which
is why safeguards must be put in place to retain data
integrity.
Why Do You Need Distributed
Transactions?

Distributed transactions are necessary when


you need to quickly update related data that is
spread across multiple databases.
For example, if you have multiple systems that track
customer information and you need to make a
universal update (like updating the mailing address)
across all records, a distributed transaction will ensure
that all records get updated.

And if a failure occurs, the data is reset to its original


state, and it is up to the originating application to
resubmit the transaction.

You might also like