database architectures and the web

29
COMP1711 Database Modelling and Knowledge Engineering Database Architectures and the Web Chapter 3

Upload: others

Post on 04-Oct-2021

6 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Database Architectures and the Web

COMP1711 Database Modelling and Knowledge Engineering

Database Architecturesand the Web

Chapter 3

Page 2: Database Architectures and the Web

Chapter 3 - Objectives

• Components of a DMBS

• Multi-user DBMS Architectures

• Web services

• Distributed DBMSs

• Data Warehousing

• Oracle Architecture

Page 3: Database Architectures and the Web

Chapter 3 - Objectives

• Components of a DMBS

• Multi-user DBMS Architectures

• Web services

• Distributed DBMSs

• Data Warehousing

• Oracle Architecture

Page 4: Database Architectures and the Web

Components of a DBMS

Page 5: Database Architectures and the Web

Components of a DBMS

Page 6: Database Architectures and the Web

Components of a DBMS

Page 7: Database Architectures and the Web

Components of Database Manager

Page 8: Database Architectures and the Web

Chapter 3 - Objectives

• Components of a DMBS

• Multi-user DBMS Architectures

• Web services

• Distributed DBMSs

• Data Warehousing

• Oracle Architecture

Page 9: Database Architectures and the Web

Multi-User DBMS Architectures

• Teleprocessing

• File-server

• Client-server

Page 10: Database Architectures and the Web

Teleprocessing

• Traditional architecture.

• Single mainframe with a number of terminals attached.

• Trend is now towards downsizing.

Page 11: Database Architectures and the Web

File-Server Architecture

DBMS on

each workstation

Page 12: Database Architectures and the Web

File-Server

• File-server is connected to several workstations across a network.

• Database resides on file-server.

• DBMS and applications run on each workstation.

• Disadvantages include:• Significant network traffic.

• Copy of DBMS on each workstation.

• Concurrency, recovery and integrity control more complex.

Page 13: Database Architectures and the Web

Traditional Two-Tier Client-Server

Applications

Page 14: Database Architectures and the Web

Traditional Two-Tier Client-Server

• Client (tier 1) manages user interface and runs applications.

• Server (tier 2) holds database and DBMS.

• Advantages include:• wider access to existing databases;

• increased performance;

• possible reduction in hardware costs;

• reduction in communication costs;

• increased consistency.

Page 15: Database Architectures and the Web

Traditional Two-Tier Client-Server

Page 16: Database Architectures and the Web

Three-Tier Client-Server

• Client side presented two problems preventing true scalability:• ‘Fat’ client, requiring considerable resources on client’s computer to run

effectively.

• Significant client side administration overhead.

• By 1995, three layers proposed, each potentially running on a different platform.

Page 17: Database Architectures and the Web

Three-Tier Client-Server

Page 18: Database Architectures and the Web

Three-Tier Client-Server

• Advantages:• ‘Thin’ client, requiring less expensive hardware.

• Application maintenance centralized.

• Easier to modify or replace one tier without affecting others.

• Separating business logic from database functions makes it easier toimplement load balancing.

• Maps quite naturally to Web environment.

Page 19: Database Architectures and the Web

Multi-user DBMS Architectures

• N-tier architectures• Three-tier architecture can be expanded to n tiers

• Application servers• Hosts an application programming interface (API) to expose business

logic and business processes for use by other applications

Page 20: Database Architectures and the Web

Chapter 3 - Objectives

• Components of a DMBS

• Multi-user DBMS Architectures

• Web services

• Distributed DBMSs

• Data Warehousing

• Oracle Architecture

Page 21: Database Architectures and the Web

Distributed DBMS

Page 22: Database Architectures and the Web

Distributed DBMSs

• Distributed database• Logically interrelated collection of shared data physically distributed

over a computer network

• Distributed DBMS• Software system that permits the management of the distributed

database

Makes the distribution transparent to users

Page 23: Database Architectures and the Web

Distributed DBMSs

• Characteristics of DDBMS• Collection of logically related shared data

• Data split into fragments

• Fragments may be replicated

• Fragments/replicas are allocated to sites

• Sites are linked by a communications network

• Data at each site is controlled by DBMS

• DMBS handles local apps autonomously

• Each DBMS in one or more global app

Page 24: Database Architectures and the Web

Distributed Processing

A centralized database that can be accessed over acomputer network.

NOT a distribute

database!

Page 25: Database Architectures and the Web

Chapter 3 - Objectives

• Components of a DMBS

• Multi-user DBMS Architectures

• Web services

• Distributed DBMSs

• Data Warehousing

• Oracle Architecture

Page 26: Database Architectures and the Web

Architecture of a Data Warehouse

Page 27: Database Architectures and the Web

Data Warehousing

• Data warehouse• Consolidated view of corporate data

• Drawn from disparate operational data sources

• Range of end-user access tools capable of supporting simple to highly complex queries to support decision making

• Subject-oriented, integrated, time-variant, and nonvolatile

Page 28: Database Architectures and the Web

Chapter 3 - Objectives

• Components of a DMBS

• Multi-user DBMS Architectures

• Web services

• Distributed DBMSs

• Data Warehousing

• Oracle Architecture

Page 29: Database Architectures and the Web