Lecture 3

Lecture 3
Architecture
Architecture
The architecture of a system defines its structure
• the components of the system are identified
• the function of each component is specified
• the interrelationships and interactions among
the components are defined.
Applies both for computer systems as well as for
software systems,
e.g, – division into modules, description of
modules, etc. – architecture of a computer
ARCHITECTURAL MODELS FOR
DISTRIBUTED DBMS
ARCHITECTURAL MODELS FOR
DISTRIBUTED DBMS
The systems are characterized with respect to:
(1) the autonomy of the local systems,
(2) their distribution,
(3) their heterogeneity
Dimension of the problem
• Distribution
– Whether the components of the system are located on the
same machine or not
• Heterogeneity
– Various levels (hardware, communications, operating system)
– DBMS important one
• data model, query language,transaction management algorithms
• Autonomy
– Not well understood and most troublesome
– Various versions
• Design autonomy: Ability of a component DBMS to decide on issues
related to its own design.
• Communication autonomy: Ability of a component DBMS to decide
whether and how to communicate with other DBMS.
• Execution autonomy: Ability of a component DBMS to execute local
operations in any manner it wants to.
ANSI/SPARC Architecture
• At the lowest level of the architecture is the
internal view, which deals with the physical
definition and organization of data.
• At the other extreme is the external view, which

is concerned with how users view the database.
• Between these two ends is the conceptual

schema, which is an abstract definition of the
database. It is the „real world” view of the
enterprise being modeled in the database.
Client server architecture
• The data processing is split into distinct parts. A part is
either requester (client) or provider (server). The client
sends during the data processing one or more requests to
the servers to perform specified tasks. The server part
provide services for the clients.
• This basic structure is called 2-tier structure
The main basic communication modes:
• - RPC, remote procedure call
• - Message-based
The client and server parts may reside on the same node or
on different nodes.
A client can be connected to several servers
• This architecture is quite common in relational systems where the
communication between the clients and the server(s) is at the level
of SQL statements.
Multiple client - single server
From a data management perspective, this is not much different
from centralized databases since the database is stored on only one
machine (the server) which also hosts the software to manage it.
However, there are some differences from centralized systems in
the way transactions are executed and caches are managed.
Multiple client - multiple server

In this case, two alternative management strategies are possible:
either 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.
Database Server
Distributed Database Servers
Data logical Distributed DBMS
Architecture
ES1 ES2 ... ESn
GCS
LCS1 LCS2
... LCSn
LIS1 LIS2 ... LISn

Peer-to-Peer Component Architecture
USER PROCESSOR DATA PROCESSOR
Global Local System Local

External
Conceptual Conceptual Log Internal
Schema Schema GD/D Schema Schema
User
requests Database
Semantic Data
Local Recovery
User Interface
Global Query
Local Query
Controller
Optimizer
Execution
Handler
Processor
Processor
Manager
Runtime
Monitor
Support
USER Global
System
responses
• user interface handler is responsible for interpreting
user commands as they come in, and formatting the
result data as it is sent to the use.
• The semantic data controller uses the integrity
constraints and authorization
• The global query optimizer and decomposer
determines translates the global queries into local ones
using the global and local conceptual schemas.
• The distributed execution monitor coordinates the
distributed execution of the user request. The
execution monitor is also called the distributed
transaction manager. In executing queries in a
distributed fashion
• The local query optimizer, which actually acts as
the access path selector, is responsible for
choosing the best access path5 to access any data
item.
• The local recovery manager is responsible for
making sure that the local database remains
consistent even when failures occur.
• The run-time support processor physically
accesses the database according to the physical
commands in the schedule generated by the
query optimizer.
Data logical Multi-DBMS Architecture
GES1 GES2 ... GESn
LES11 … LES1n GCS LESn1 … LESnm
LCS1 LCS2 … LCSn
LIS1 LIS2 … LISn

DIFFERENCE BETWEEN data logical
distributed DBMS and Datalogical
Multi-DBMS
In the case of logically integrated distributed DBMSs, the global conceptual
schema defines the conceptual view of the entire database, while in the case
of distributed multi-DBMSs, it represents only the collection of some of the
local databases that each local DBMS wants to share
MDBS Components & Execution
Global
User
Request
Local Local
User Multi-DBMS User
Request Layer Request
Global Global Global
Subrequest Subrequest Subrequest
DBMS1 DBMS2 DBMS3

The fundamental difference is the existence of full-
fledged DBMSs, each of which manages a different
database. The MDBS provides a layer of software that
runs on top of these individual DBMSs and provides
users with the facilities of accessing various databases
(Figure 1.17). Note that in a distributed MDBS, the
multi-DBMS layer may run on multiple sites or there
may be central site where those services are offered.
Mediator/Wrapper Architecture
• The mediators(is a sw) typically operate using
a common data model and interface language.
To deal with potential heterogeneities of the
source DBMSs, wrappers are implemented
whose task is to provide a mapping between a
source DBMSs view and the mediators’ view.
• One can view the collection of mediators as a
middleware layer that provides services above
the source systems

Lecture 3

Uploaded by

Lecture 3

Uploaded by

Lecture 3

• At the other extreme is the external view, which

• Between these two ends is the conceptual

Multiple client - multiple server

LIS1 LIS2 ... LISn

Global Local System Local

GES1 GES2 ... GESn

LES11 … LES1n GCS LESn1 … LESnm

LCS1 LCS2 … LCSn

LIS1 LIS2 … LISn

DBMS1 DBMS2 DBMS3

You might also like