Scribd
Upload
45 views

1) Client Server Architectures

The document discusses three distributed database management system (DDBS) architectures: 1) client-server, where the server performs most data management work and the client manages cached data; 2) peer-to-peer, which uses local and global conceptual schemas to handle data fragmentation and replication across sites; and 3) multi-database systems (MDBS), which integrate local databases and define global schemas for shared data.

Uploaded by

sarmad khan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
45 views

1) Client Server Architectures

The document discusses three distributed database management system (DDBS) architectures: 1) client-server, where the server performs most data management work and the client manages cached data; 2) peer-to-peer, which uses local and global conceptual schemas to handle data fragmentation and replication across sites; and 3) multi-database systems (MDBS), which integrate local databases and define global schemas for shared data.

Uploaded by

sarmad khan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

In previous lecture:

- DDBS Architecture

In this lecture:
- DDBS Architecture continued

Distributed DBMS Architecture:


The three distributed DBMS architecture are discussed below:

1) Client Server Architectures:


The term is used here in different meanings: generally Client and Server refer to processes may
be running at same machine in the context of DDBS both client and server are machines not
process.

Server:
Server does most of the data management work. This means that all of the query processing
and optimization, transaction management and storage management is done at the server.

Client:
Application and user interface has a DBMS client module that is responsible for managing the
data that is cached to the client and managing the transaction locks that may have been cached
as well. Consistency checking of user queries is also applied at the client side.

Working
The client passes SQL queries to the server without trying to understand or optimize them. The
server does most of the work and returns the result relation to the client.

Types
There are number of different types of client/server architecture.
1) Multiple client single server
There is only one server which is accessed by multiple clients.

2) Multiple client multiple server


Two alternative management strategies are possible: wither each client manages its own
connection to the appropriate server or each client knows of only its home server which then
communicates with other servers as required.

2) Peer to Peer Distributed System:


Physical data organization on each machine may be different. This means that there needs to be
an individual internal schema definition at each site which we call the local internal schema
(LIS). The enterprise view of the data is described by the global conceptual schema (GCS),
which is global because it describes the logical structure of the data at all the sites.
In distributed database data is fragmented and replicated. To handle this phenomenon of
fragmentation and replication, the logical organization of data at each site needs to be described.
There needs to be a third layer in the architecture, the local conceptual schema (LCS). The global
conceptual schema is the union of the local conceptual schemas. User applications and user
access to the database is supported by external schemas (ESs).
This architectural model is shown in figure 1. Data independence is supported. Localization and
replication transparencies are supported by the definition of local and global conceptual schemas
and the mapping in between. Network transparency is supported by the definition of global
conceptual schema.

ES1 ES2 ES1 ESn

GCS

LCS1 LCS2 LCSn

LIS1 LIS LIS


Figure 1: Distributed Database Reference Architecture
Components
The components of distributed DBMS are shown in figure 2. One component handles the
interaction with users and other deals with the storage. The first components is called
user processor, consists of four elements.
1. The user interface handler is responsible for interpreting user commands and formatting
the result data as it is sent to the user.
2. The semantic data controller uses the integrity constraints and authorizations that are
defined as part of the global conceptual schema to check if the user query can be
processed.
3. The global query optimizer and decomposer determines an execution strategy to
minimize a cost function and translates the global queries into local ones using global
and local conceptual schema as well as global directory. The global query optimizer is
responsible for generating the best strategy to execute distributed join operations.
4. The distributed execution monitor coordinates the distributed execution of the user
request. The execution monitor is also called the distributed transaction manager.
The second major component of a distributed DBMS is the data processor and consists of three
elements.
1. The local query optimizer, which actually acts as the access path selector, is responsible
for choosing the best path to access any data item.
2. The local recovery manager is responsible for making sure that the local
database remains consistent even when failures occur.
3. The run-time support processor physically accesses the database accordin to the
physical commands in the schedule generated by the query optimizer. The run-
time support processor is the interface to the operating system and contains the
database buffer manager which is responsible for main memoy buffers and data
accesses.
Figure 2: Components of a Distributed DBMS

MDBS Architecture:
The differences in the level of autonomy between the distributed multi-DBMSs and distributed
DBMSs are also reflected in their architecture models. The fundamental difference relates to the
definition of global conceptual schema. In case of logically integrated distributed DBMSs, the
global conceptual schema defines the conceptual view of the entire database, while in case of
distributed multi DBMSs; it represents only the collection of some of the local databases that
each local DBMS wants to share. Thus the definition of global database is different in MDBSs
than in distributed DBMSs.

Models Using a Global Conceptual Schema


Designing the global conceptual schema in multi-database systems involve
the integration of either the local conceptual schemas or the local external
schemas. A major difference between the deign of the GCS in the multi-
DBMSs and in logically integrated distributed DBMSs is that in the former
the mapping is from local conceptual schemas to a global schema.
Once the GCS has been designed, views over the global schema can be
defined for users who require global access. It is not necessary for the GES
and GCS to be defined using the same data model and language, whether
they do or not determines whether the system is homogenous and
heterogeneous.
If heterogeneity exists in the system, then two implementation alternatives
exist: unilingual and multilingual. A unilingual multi-DBMS requires the
users to utilize possibly different data models and languages when both a
local database and the global database are accessed. One application may
have a local external schema (LES) defined on local conceptual schema as
well as global external schema (GES) defined on the global conceptual
schema.
A multilingual architecture, where the basic philosophy is to
permit each user to access the global database by means of an
external schema.

Models without a Global Conceptual Schema


In this architecture there are two layers: the local system layer and the
multi database layer on the top of it. The local system layer consist of a
number of DBMSs, which present to the multi database layer the part of
their local database they are willing to share with users of other
databases. If heterogeneity is involved, each of these schemas, LCSi may
use a different data model.
External views are constructed where each view may be defined on one
local conceptual schema or on a multiple conceptual schemas. Thus the
responsibility of providing access to multiple databases is delegated to the
mapping between the external schemas and the local conceptual schemas.
The component based architectural model of a multi-DBMS is
significantly different from a distributed DBMS.

Summary:
We have discussed the three distributed DBMS architecture. These
architectures are Client and Server architecture, peer to peer
architecture and multi database system architecture.

You might also like