DISTRIBUTED

DBMS
ARCHITECTURE

Covered Topics
What is Architecture? DBMS Architecture
Three levels of DBMS architecture
Architectural Model for DDBMSs

Three dimensions:
Autonomy
Distribution
Heterogeneity

What is Architecture?
The architecture of a system defines its structure
- it is an idealized view
real world systems may be different
yet it shows the essential components

DBMS Architecture
Based on components.
A DBMS consists of a number of components, each of which provides
some functionality.

Based on functions.
The different classes of users are identified and the functions that the
system will perform for each class are defined.

Based on data.
The different types of data are identified, and an architectural framework
is specified which defines the use of data according to different views.

DBMS Architecture

Three levels of DBMS architecture

External Level
Users view of the DB. This level describes that part of the DB
that is relevant to each user

Logical or Conceptual Level

Describes what data are stored in the DB & what relationships
exist among those data
Describes the entire DB in terms of relatively simpler structures

Internal Level
Internal level indicates hoe the data will be stored and
described the access method to be used by the database.

Architectural Model for DDBMSs

Architectural Models for DDBMSs (or more
generally for multiple DBMSs) can be classified
along three dimensions:
Autonomy
Distribution
Heterogeneity

ARCHITECTURAL MODEL FOR DISTRIBUTED DBMSs

ARCHITECTURAL MODEL FOR DISTRIBUTED DBMSs -

AUTONOMY
Autonomy refers to the distribution of control. It indicates the
degree to which individual DBMSs can operate independently.
Three alternatives:

Tight integration
Semi-autonomous
Total isolation

ARCHITECTURAL MODEL FOR DISTRIBUTED DBMSs -

AUTONOMY
Tight integration.
A single-image of the entire database is available to any user who wants
to share the information, which may reside in multiple databases. From
the users perspective, the data is logically centralized in one database.

Semi-autonomous systems.
The DBMSs can operate independently. Each of these DBMSs determine
what parts of their own database they will make accessible to users of
other DBMSs.

Total isolation.
The individual systems are stand-alone DBMSs, which know neither of
the existence of the other DBMSs nor how to communicate with them.

ARCHITECTURAL MODELS FOR DISTRIBUTED DBMSs

DISTRIBUTION

Distributions refers to the distributions of data.

we are considering the physical distribution of
data over multiple sites; the user sees the data
as one logical pool.
Two alternatives:
client / server distribution
peer-to-peer distribution

ARCHITECTURAL MODELS FOR DISTRIBUTED DBMSs

DISTRIBUTION
Client / server distribution.
The client / server distribution concentrates data management
duties at servers while the clients focus on providing the
application environment including the user interface. The
communication duties are shared between the client machines
and servers. Client / server DBMSs represent the first attempt
at distributing functionality.

Peer-to-peer distribution.
There is no distinction of client machines versus servers. Each
machine has full DBMS functionality and can communicate
with other machines to execute queries and transactions.

Peer-to-Peer Architecture for DDBMS (Data-based)

Local internal schema (LIS)
Describes the local physical data organization
(which might be different
on each machine)
Local conceptual schema (LCS)
Describes logical data organization
at each site
Required since the data are fragmented
and replicated
Global conceptual schema (GCS)
Describes the global logical view of
the data
Union of the LCSs
External schema (ES)
Describes the user/application view
on the data

ARCHITECTURAL MODELS FOR DISTRIBUTED DBMSs

HETEROGENEITY
Refers to heterogeneity of the components at various levels
Hardware
Communications
Operating system
DB components

Conclusion
Architecture defines the structure of the system. There
are three ways to define the architecture:
based on components, functions, or data
3 level Architecture defines external, conceptual, and
internal schemas
There are three dimensions for DDBMS:
level of distribution, autonomy, and heterogeneity

Thank You