Scribd
Upload
3 views

Distributed Database System

Uploaded by

charndeeo
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
3 views

Distributed Database System

Uploaded by

charndeeo
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Distributed Database

System
Introduction

 A distributed database is basically a database that is


not limited to one system, it is spread over different
sites, i.e, on multiple computers or over a network of
computers. A distributed database system is located
on various sites that don’t share physical components.
This may be required when a particular database
needs to be accessed by various users globally. It
needs to be managed such that for the users it looks
like one single database.
Architecture
Features

• It is used to create, retrieve, update and delete distributed databases.


• It synchronizes the database periodically and provides access mechanisms
by the virtue of which the distribution becomes transparent to the users.
• It ensures that the data modified at any site is universally updated.
• It is used in application areas where large volumes of data are processed
and accessed by numerous users simultaneously.
• It is designed for heterogeneous database platforms.
• It maintains confidentiality and data integrity of the databases.
Types
 1. Homogeneous Database:
In a homogeneous database, all different sites store database
identically. The operating system, database management system,
and the data structures used – all are the same at all sites. Hence,
they’re easy to manage.
 2. Heterogeneous Database:
In a heterogeneous distributed database, different sites can use
different schema and software that can lead to problems in query
processing and transactions. Also, a particular site might be
completely unaware of the other sites. Different computers may use
a different operating system, different database application. They
may even use different data models for the database. Hence,
translations are required for different sites to communicate.
Distributed Data Storage

 There are 2 ways in which data can be stored on different sites. These
are:
 1. Replication –
In this approach, the entire relationship is stored redundantly at 2 or
more sites. If the entire database is available at all sites, it is a fully
redundant database. Hence, in replication, systems maintain copies of
data.
 This is advantageous as it increases the availability of data at different
sites. Also, now query requests can be processed in parallel.
However, it has certain disadvantages as well. Data needs to be
constantly updated. Any change made at one site needs to be recorded
at every site that relation is stored or else it may lead to inconsistency.
This is a lot of overhead. Also, concurrency control becomes way more
complex as concurrent access now needs to be checked over a number
of sites.
Distributed Data Storage
 2. Fragmentation –
In this approach, the relations are fragmented (i.e., they’re divided into
smaller parts) and each of the fragments is stored in different sites where
they’re required. It must be made sure that the fragments are such that they
can be used to reconstruct the original relation (i.e, there isn’t any loss of
data).
Fragmentation is advantageous as it doesn’t create copies of data,
consistency is not a problem.

 Fragmentation of relations can be done in two ways:

• Horizontal fragmentation – Splitting by rows –


The relation is fragmented into groups of tuples so that each tuple is
assigned to at least one fragment.
• Vertical fragmentation – Splitting by columns –
The schema of the relation is divided into smaller schemas. Each fragment
must contain a common candidate key so as to ensure a lossless join.
Factors Encouraging DDBMS
 The following factors encourage moving over to DDBMS −
• Distributed Nature of Organizational Units − Most organizations in the current times are
subdivided into multiple units that are physically distributed over the globe. Each unit requires
its own set of local data. Thus, the overall database of the organization becomes distributed.
• Need for Sharing of Data − The multiple organizational units often need to communicate
with each other and share their data and resources. This demands common databases or
replicated databases that should be used in a synchronized manner.
• Support for Both OLTP and OLAP − Online Transaction Processing (OLTP) and Online
Analytical Processing (OLAP) work upon diversified systems which may have common data.
Distributed database systems aid both these processing by providing synchronized data.
• Database Recovery − One of the common techniques used in DDBMS is replication of data
across different sites. Replication of data automatically helps in data recovery if database in
any site is damaged. Users can access data from other sites while the damaged site is being
reconstructed. Thus, database failure may become almost inconspicuous to users.
• Support for Multiple Application Software − Most organizations use a variety of
application software each with its specific database support. DDBMS provides a uniform
functionality for using the same data among different platforms.
Adversities of Distributed Databases
 Following are some of the adversities associated with distributed
databases.
• Need for complex and expensive software − DDBMS demands
complex and often expensive software to provide data transparency and
co-ordination across the several sites.
• Processing overhead − Even simple operations may require a large
number of communications and additional calculations to provide
uniformity in data across the sites.
• Data integrity − The need for updating data in multiple sites pose
problems of data integrity.
• Overheads for improper data distribution − Responsiveness of
queries is largely dependent upon proper data distribution. Improper
data distribution often leads to very slow response to user requests.

You might also like