Scribd
Upload
16 views

Unit 1.3 - Distributed Databases

Uploaded by

RashmiRavi Naik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

Unit 1.3 - Distributed Databases

Uploaded by

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

Before SOA After SOA

Siloed • Closed • Monolithic • Brittle Shared services • Collaborative • Interoperable • Integrated

Application Dependent Business Functions


Service Order Account Composite
scheduling processing management application

Composed
Check customer Check customer Calculate shipping business process
status status charges
Determine product oduct
Order status
availability availability Reusable Business Services
Verify
Check credit
customer credit Reusable Create Check Check Reusable
Order status service invoice customer order service
status status

Reusable Reusable Check Check Reusable


service service credit inventory service

Data External Data External


Marketing Sales CRM Marketing Sales Finance
warehouse partner warehouse partner

3.3 Distributed DBMSs


As discussed in Chapter 1, a major motivation behind the development of data-
base systems is the desire to integrate the operational data of an organization and
to provide controlled access to the data. Although we may think that integration
and controlled access implies centralization, this is not the intention. In fact, the
development of computer networks promotes a decentralized mode of work. This

M03_CONN3067_06_SE_C03.indd 120 06/06/14 4:52 PM


decentralized approach mirrors the organizational structure of many companies,
which are logically distributed into divisions, departments, projects, and so on, and
physically distributed into offices, plants, or factories, where each unit maintains
its own operational data. The development of a distributed DBMS that reflects
this organizational structure, makes the data in all units accessible, and stores data
proximate to the location where it is most frequently used, should improve the
ability to share the data and should improve the efficiency with which we can access
the data.

Distributed A logically interrelated collection of shared data (and a description


database of this data), physically distributed over a computer network.

Distributed The software system that permits the management of the distrib-
DBMS uted database and makes the distribution transparent to users.

A distributed database management system (DDBMS) consists of a single logical


database that is split into a number of fragments. Each fragment is stored on one or
more computers (replicas) under the control of a separate DBMS, with the comput-
ers connected by a communications network. Each site is capable of independently
processing user requests that require access to local data (that is, each site has some
degree of local autonomy) and is also capable of processing data stored on other
computers in the network.
Users access the distributed database via applications. Applications are classified
as those that do not require data from other sites (local applications) and those that
do require data from other sites (global applications). We require a DDBMS to have at
least one global application. A DDBMS therefore has the following characteristics:
• a collection of logically related shared data;
• data split into a number of fragments;
• fragments may be replicated;
• fragments/replicas are allocated to sites;
• sites are linked by a communications network;
• data at each site is under the control of a DBMS;
• DBMS at each site can handle local applications, autonomously;
• each DBMS participates in at least one global application.

It is not necessary for every site in the system to have its own local database, as
illustrated by the topology of the DDBMS shown in Figure 3.11.
From the definition of the DDBMS, the system is expected to make the distribu-
tion transparent (invisible) to the user. Thus, the fact that a distributed database is
split into fragments that can be stored on different computers and perhaps repli-
cated should be hidden from the user. The objective of transparency is to make the
distributed system appear like a centralized system. This is sometimes referred to
as the fundamental principle of distributed DBMSs. This requirement provides sig-
nificant functionality for the end-user but, unfortunately, creates many additional
problems that have to be handled by the DDBMS.

www.EBooksWorld.ir
M03_CONN3067_06_SE_C03.indd 121 06/06/14 4:52 PM
Figure 3.11
Distributed
database
management
system.

Distributed processing
It is important to make a distinction between a distributed DBMS and distributed
processing:

Distributed A centralized database that can be accessed over a computer network.


processing

The key point with the definition of a distributed DBMS is that the system consists
of data that is physically distributed across a number of sites in the network. If the data
is centralized, even though other users may be accessing the data over the network, we
do not consider this to be a distributed DBMS simply distributed processing. We illus-
trate the topology of distributed processing in Figure 3.12. Compare this figure, which
has a central database at site 2, with Figure 3.11, which shows several sites each with
their own database. We will discuss distributed DBMSs in depth in Chapters 24 and 25.

Figure 3.12
Distributed
processing.

www.EBooksWorld.ir
M03_CONN3067_06_SE_C03.indd 122 06/06/14 4:52 PM

You might also like