ADBMS Chapter1 Architectures PDF

Chapter 1: Database System Architectures
Database System Concepts, 6th Ed.

Silberschatz, Korth and Sudarshan
See www.db-book.com for conditions on re-use
Database System Architectures

1.1 Centralised
1.2 Client-Server
1.3 Server system
Transaction servers
Data servers
Cloud based servers
1.4 Parallel
1.5 Distributed
1.6 Web based system
Web architecture (2 tier , 3 tier, N-tier Architecture)
Web services SOAP
Database System Concepts - 6th Edition
17.2
Centralized Systems
Run on a single computer system and do not interact with other
computer systems.
General-purpose computer system: one to a few CPUs and a number
of device controllers that are connected through a common bus that

provides access to shared memory.
Single-user system (e.g., personal computer or workstation): desk-top
unit, single user, usually has only one CPU and one or two hard
disks; the OS may support only one user.
Multi-user system: more disks, more memory, multiple CPUs, and a
multi-user OS. Serve a large number of users who are connected to

the system vie terminals. Often called server systems.
17.3
A Centralized Computer System
17.4
Client--Server Systems
Client
Server systems satisfy requests generated at m client systems, whose
general structure is shown below:
17.5
Client--Server Systems (Cont.)

Client
Database functionality can be divided into:
Back-end: manages access structures, query evaluation and

optimization, concurrency control and recovery.
Front-end: consists of tools such as forms, report-writers, and

graphical user interface facilities.
The interface between the front-end and the back-end is through SQL or
through an application program interface.
17.6
Client--Server Systems (Cont.)

Client
Advantages of replacing mainframes with networks of workstations or
personal computers connected to back-end server machines:

better functionality for the cost
flexibility in locating resources and expanding facilities
better user interfaces
easier maintenance
17.7
Server System Architecture

Server systems can be broadly categorized into two kinds:
transaction servers which are widely used in relational database

systems, and
data servers, used in object-oriented database systems
17.8
Transaction Servers
Also called query server systems or SQL server systems
Clients send requests to the server
Transactions are executed at the server
Results are shipped back to the client.
Requests are specified in SQL, and communicated to the server
through a remote procedure call (RPC) mechanism.

Transactional RPC allows many RPC calls to form a transaction.
Open Database Connectivity (ODBC) is a C language application
program interface standard from Microsoft for connecting to a server,

sending SQL requests, and receiving results.
Log writer process
Server processes simply add log records to log record buffer
Log writer process outputs log records to stable storage.
Checkpoint process
Performs periodic checkpoints
17.9
Transaction Server Process Structure

A typical transaction server consists of multiple processes accessing
data in shared memory.

Server processes
These receive user queries (transactions), execute them and send

results back
Processes may be multithreaded, allowing a single process to

execute several user queries concurrently
Typically multiple multithreaded server processes
Lock manager process

More on this later
Database writer process

Output modified buffer blocks to disks continually
17.10
Transaction Server Processes (Cont.)

Log writer process
Server processes simply add log records to log record buffer
Log writer process outputs log records to stable storage.
Checkpoint process
Performs periodic checkpoints
Process monitor process

Monitors other processes, and takes recovery actions if any of

the other processes fail
E.g., aborting any transactions being executed by a server

process and restarting it
17.11
17.12
Transaction System Processes (Cont.)

Shared memory contains shared data
Buffer pool
Lock table
Log buffer
Cached query plans (reused if same query submitted again)
All database processes can access shared memory
To ensure that no two processes are accessing the same data structure
at the same time, databases systems implement mutual exclusion
using either
Operating system semaphores
Atomic instructions such as test-and-set
To avoid overhead of interprocess communication for lock
request/grant, each database process operates directly on the lock

table
instead of sending requests to lock manager process
Lock manager process still used for deadlock detection
17.13
Data Servers
Used in high-speed LANs, in cases where
The clients are comparable in processing power to the server
The tasks to be executed are compute intensive.
Data are shipped to clients where processing is performed, and then
shipped results back to the server.

This architecture requires full back-end functionality at the clients.
Used in many object-oriented database systems
Issues:
Page-Shipping versus Item-Shipping
Locking
Data Caching
Lock Caching
17.14
Data Servers (Cont.)

Page-shipping versus item-shipping
Smaller unit of shipping more messages
Worth prefetching related items along with requested item

Page shipping can be thought of as a form of prefetching
Locking
Overhead of requesting and getting locks from server is high due
to message delays
Can grant locks on requested and prefetched items; with page
shipping, transaction is granted lock on whole page.
Locks on a prefetched item can be P{called back} by the server,
and returned by client transaction if the prefetched item has not
been used.
Locks on the page can be deescalated to locks on items in the

page when there are lock conflicts. Locks on unused items can
then be returned to server.
17.15
Data Servers (Cont.)

Data Caching
Data can be cached at client even in between transactions
But check that data is up-to-date before it is used (cache

coherency)
Check can be done when requesting lock on data item
Lock Caching
Locks can be retained by client system even in between

transactions
Transactions can acquire cached locks locally, without

contacting server
Server calls back locks from clients when it receives conflicting

lock request. Client returns lock once no local transaction is
using it.
Similar to deescalation, but across transactions.
17.16
Cloud based servers

A database accessible to clients from
the cloud and delivered to users on

demand via the Internet from a cloud
database provider's servers. Also
referred to as Database-as-a-Service
(DBaaS), cloud databases can use
cloud computing to achieve optimized
scaling, high availability, multi-tenancy
and effective resource allocation.
17.17
Cloud based servers
17.18
Cloud based servers

Cloud databases can offer significant advantages
over their traditional counterparts, including

increased accessibility, automatic failover and fast
automated recovery from failures, automated on-thego scaling, minimal investment and maintenance of
in-house hardware, and potentially better
performance.
At the same time, cloud databases have their share
of potential drawbacks, including security and

privacy issues as well as the potential loss of or
inability to access critical data in the event of a
disaster or bankruptcy of the cloud database service
provider.
17.19
Web based system

Significance of Tiers
N-tier architectures have the same
components
Presentation
Business/Logic
Data
N-tier architectures try to separate the
components into different tiers/layers

Tier: physical separation
Layer: logical separation
17.20
1-Tier Architecture
All 3 layers are on the same machine
All code and processing kept on a single machine
Presentation, Logic, Data layers are tightly connected
Scalability: Single processor means hard to increase volume of processing
Portability: Moving to a new machine may mean rewriting everything
Maintenance: Changing one layer requires changing other layers
17.21
2-Tier Architecture
Database runs on Server
Separated from client
Easy to switch to a different database
Presentation and logic layers still tightly connected
Heavy load on server
Potential congestion on network
Presentation still tied to business logic
17.22
3-Tier Architecture
Each layer can potentially run on a different machine
Presentation, logic, data layers disconnected
17.23
Web Services
eXtensible Markup Language (XML)
Simple Object Access Protocol (SOAP)
Web Services Description Language
(WSDL)
Directory Services
Universal Description, Discovery, and
Integration (UDDI)
17.24
Standards for Web Services
25
Database System Concepts -
6th
Edition
17.25
SOAP (Simple Object Access Protocol)

Used to exchange messages via HTTP, SMTP, and
SIP (Session Initiation Protocol for Internet

telephony)
Originally designed for remote-procedure calls (RPC)
Works through firewalls on port 80
Character-based, so easy to encrypt/decrypt and
thus easy to secure

Inefficient due to character, not binary, data and large
headers
Does not describe bidirectional or n-party interaction
17.26
Ex. SOAP Request

POST /temp HTTP/1.1
Host: www.socweather.com
Content-Type: text/xml; charset="utf-8"
Content-Length: xxx
SOAPAction: "http://www.socweather.com/temp"

<!These comments and below: an XML document -->
<?xml version=1.0?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
<env:Body>
<m:GetTemp xmlns:m="http://www.socweather.com/temp.xsd">
<m:City>Honolulu</m:City>
<m:When>now</m:When>
</m:GetTemp>
</env:Body>
</env:Envelope>
17.27
Ex. SOAP Response

HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Content-Length: xxx
SOAPAction: "http://www.socweather.com/temp"
<?xml version="1.0"?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
<env:Body>
<m:GetTempResponse
xmlns:m="http://www.socweather.com/temp.xsd">
<m:DegreesCelsius>30</m:DegreesCelsius>
</m:GetTempResponse>
</env:Body>
</env:Envelope>
17.28

ADBMS Chapter1 Architectures PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ADBMS Chapter1 Architectures PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Chapter 1: Database System Architectures

Database System Concepts, 6th Ed.

Database System Architectures

Cloud based servers

Web architecture (2 tier , 3 tier, N-tier Architecture)

Web services SOAP

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

of device controllers that are connected through a common bus that

multi-user OS. Serve a large number of users who are connected to

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

A Centralized Computer System

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

general structure is shown below:

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

Client--Server Systems (Cont.)

Back-end: manages access structures, query evaluation and

Front-end: consists of tools such as forms, report-writers, and

through an application program interface.

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

Client--Server Systems (Cont.)

personal computers connected to back-end server machines:

better functionality for the cost

flexibility in locating resources and expanding facilities

better user interfaces

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

Server System Architecture

transaction servers which are widely used in relational database

data servers, used in object-oriented database systems

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

Clients send requests to the server

Transactions are executed at the server

Results are shipped back to the client.

Requests are specified in SQL, and communicated to the server

through a remote procedure call (RPC) mechanism.

program interface standard from Microsoft for connecting to a server,

Server processes simply add log records to log record buffer

Log writer process outputs log records to stable storage.

Performs periodic checkpoints

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

Transaction Server Process Structure

data in shared memory.

These receive user queries (transactions), execute them and send

Processes may be multithreaded, allowing a single process to

Typically multiple multithreaded server processes

Lock manager process

More on this later

Database writer process

Output modified buffer blocks to disks continually

Database System Concepts - 6th Edition

Silberschatz, Korth and Sudarshan

Transaction Server Processes (Cont.)

Server processes simply add log records to log record buffer

Log writer process outputs log records to stable storage.

Performs periodic checkpoints