Architecture Model of Distributed Database Management System (DDBMS)
Architecture Models for DDBMSs (or more generally for multiple DBMSs) canbe classiﬁed along three dimensions:
- – Autonomy
- – Distribution
- – Heterogeneity
- Distribution − It states the physical distribution of data across the different sites.
- Autonomy − It indicates the distribution of control of the database system and the degree to which each constituent DBMS can operate independently.
- Heterogeneity − It refers to the uniformity or dissimilarity of the data models, system components and databases.
Some of the common architectural models are
- Client – Server Architecture for DDBMS
- Peer – to – Peer Architecture for DDBMS
- Multi – DBMS Architecture
1. Client – Server Architecture for DDBMS
This is a two-level architecture where the functionality is divided into servers and clients. The server functions primarily encompass data management, query processing, optimization and transaction management. Client functions include mainly user interface. However, they have some functions like consistency checking and transaction management.
The two different client – server architecture are −
- Single Server Multiple Client
- Multiple Server Multiple Client
2. Peer- to-Peer Architecture for DDBMS
In these systems, each peer acts both as a client and a server for imparting database services. The peers share their resource with other peers and co-ordinate their activities.
This architecture generally has four levels of schemas −
- Global Conceptual Schema − Depicts the global logical view of data.
- Local Conceptual Schema − Depicts logical data organization at each site.
- Local Internal Schema − Depicts physical data organization at each site.
- External Schema − Depicts user view of data.
3. Multi – DBMS Architectures
This is an integrated database system formed by a collection of two or more autonomous database systems.
Multi-DBMS can be expressed through six levels of schemas −
- Multi-database View Level − Depicts multiple user views comprising of subsets of the integrated distributed database.
- Multi-database Conceptual Level − Depicts integrated multi-database that comprises of global logical multi-database structure definitions.
- Multi-database Internal Level − Depicts the data distribution across different sites and multi-database to local data mapping.
- Local database View Level − Depicts public view of local data.
- Local database Conceptual Level − Depicts local data organization at each site.
- Local database Internal Level − Depicts physical data organization at each site.
There are two design alternatives for multi-DBMS −
- Model with multi-database conceptual level.
- Model without multi-database conceptual level.