Scribd
Upload
14 views4 pages

Data Architecture Handout

The document outlines various data architecture models, including two-tier and three-tier architectures, detailing the distribution of data and business logic across client and server tiers. It distinguishes between 'fat client' and 'thin client' architectures based on where business logic is processed. Additionally, it discusses n-tier distributed architecture and the concept of logical versus physical tiers in system design.

Uploaded by

Pratik Chatterjee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views4 pages

Data Architecture Handout

The document outlines various data architecture models, including two-tier and three-tier architectures, detailing the distribution of data and business logic across client and server tiers. It distinguishes between 'fat client' and 'thin client' architectures based on where business logic is processed. Additionally, it discusses n-tier distributed architecture and the concept of logical versus physical tiers in system design.

Uploaded by

Pratik Chatterjee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Participant Notes

Systems Analysis Lifecycle

Enterprise Requirements Conceptual Logical


Analysis Analysis Data Data
Modeling Modeling

Use Case Prototyping


Analysis and RAD

Physical
Database
Design

Multi-Tier Data Architectures

1
Participant Notes

Two-Tier Architecture with


Business Logic on the Client
• Data and business logic is distributed two tiers. The data is within a DBMS housed on a
server while the user interacts through a client interface.
• This client/server architecture is often called a “fat client” architecture.
• Business logic, including constraint and integrity checking and calculations, are
performed on the client (either a desktop client application, a mobile app, or a browser-
based client).
• Client also contains user interface logic.
Application &
Business Logic
Data Retrieved via
SQL over Network Web Client

SQL
Desktop Client
Data
DBMS Physical or User Interface
Virtual Server

Mobile App

Two-Tier Architecture with


Business Logic on the Server
• Data and business logic is distributed two tiers. The data is within a DBMS housed
on a server while the user interacts through a client interface.
• This client/server architecture is often called a “thin client” architecture.
• Business logic, including constraint and integrity checking and calculations, are
performed on the database within the server using triggers and stored procedures.
• Client hosts user interface logic only.

Application &
Business Logic
Data Retrieved via
Stored Procedure
Calls over Network
User Interface
EXEC
(Desktop Client,
App, or Web
Data
DBMS Physical or Client)
Virtual Server

2
Participant Notes

Three-Tier Architecture with


Application Server
• Data is on data server and all business logic resides on an application server.
• Communication between the “thin client” is done through remote procedure
invocation technology such as WebRPC, SOAP, or custom communication
protocols.

Business Logic
SQL Request

Data Result

Application User Interface


DBMS Data Server (Desktop Client,
Server App, or Web
Client)

n-Tier Distributed Architecture


• Data and business logic is distributed across tiers using combinations of triggers,
stored procedures, and business logic on an application server.
• This is the preferred architectural model if the data is distributed across several
(possibly disparate) databases.
• A transaction manager often handles distributed transaction logic, although this
logic is often co-located on the application server (logical tiers).

SQ User Interface
L Transaction Logic
DBMS1 D
at Logic
a Business Logic
Request

Result

DBMS2 a Transaction User Interface


at Manager Application (Desktop Client,
D
Integrity
a th Server App, or Web
Logic
XP Client)

DBMS3

3
Participant Notes

Physical vs Logical Tiers


• The tiers do not have to be physical tiers, i.e., the server does not have to be a
separate computer or virtual machine.
• A single computer or virtual machine can host all the tiers leading to a logical two-
tier or multi-tier architecture.

Application &
Business Logic
Data Retrieved via
SQL over IPC

SQL
User Interface
(Desktop Client,
Data App, or Web
DBMS Physical or
Virtual Server Client)

Logical Two-Tier Client/Server Architecture with a Thin Client

Summary, Review, & Questions…

You might also like