Three Tier Architecture
Introduction to 3-Tier Architecture
Tier is collection of logically related but Physically
Independent Components
Application is divided into 3-Tiers
Data Storage Mechanism
Introduction to 3-Tier Architecture
There is boundary of each Tier
Several Layers can join to make something Whole
Each Tier contribute toward Whole
Three Tier Architecture
Rationale for 3-Tier Architecture
To easy the development Process
Different Teams can work on different Tiers
Three Tier Architecture
Rationale for 3-Tier Architecture
To Avoid Single-point of Failure in the Application
Failure of One-Tier does not mean Application
Crash
Three Tier Architecture
External Level (Client Interface)
This is Top-Most Layer of 3-Tier Architecture
Generally refer as “Presentation Layer”
It display what Client View
Three Tier Architecture
External Level (Client Interface)
Responsible for Formatting the Data (Content)
into Presentable Form
Communicate with One-Tier Below
Browser, Forms, Mobile Application
Three Tier Architecture
Conceptual Level (Business Logic)
Second Layer of 3-Tier Architecture
Responsible for business Processing
Logic of the business is encapsulated –
Programming / Class Diagram / ERD
Three Tier Architecture
Conceptual Level (Business Logic)
BL can receive request from Presentation Layer
only
Can send response to Presentation Layer only
It can send request to One-Layer below
Three Tier Architecture
Internal Level (Data Level)
Responsible for Data Storage - Repository
Can Receive request from to Logic Layer only
Can sent response to Logic Layer only
Three Tier Architecture
Internal Level (Data Level)
All the decision regarding Data Storage are
encapsulated
Internal Storage mechanism are independent of
other Tiers – SQL, DDL, DML
Three Tier Architecture
Layer Independence
Each Tier is totally unaware about internal working
of other Tier
All the decisions in Tiers are independent of other
Tiers
Three Tier Architecture
Layer Independence
Data Layer is not aware of internal working of
Logic Layer
Logic Layer is not concerned about Data Tier
working
Presentation layer is independent of BL
Three Tier Architecture
Three Tier Architecture
Example: Presentation Layer Independence
Need to run sales query.
Output format – Browser or Form or Mobile App
can’t effect way it is retrieved
Data Storage Mechanism
Three Tier Architecture
Example: Logical Layer Independence
Get list of all sales made last year
Using If – then – else or while loop or any other
structure is internal to tier only
It can’t effect the way it is displayed
Three Tier Architecture
Three Tier Architecture
Example: Data Layer Independence
Query to fetch results
Query can be made of different component –
independent
DBMS selection can’t effect result return
Three Tier Architecture
Three Tier Architecture
Roles in Database Management System
Application Programmer
End User
Database Administrator
System Analyst
Three Tier Architecture
Client Server Architecture
Single Server to process multiple requests
Client(s) send request
Server send the response
Three Tier Architecture
Client Server Architecture
2-Tier Architecture
Server is powerful in terms of processing
Client contact Server when additional
functionality is not available on local PC
Three Tier Architecture
Three Tier Architecture
Example - Client Server Architecture
Chat Example
Communication between multiple clients with
multiple clients.
Simultaneous data exchange is manage by Server
Three Tier Architecture
Three Tier Architecture
Distributed Processing
Distributed system is combination of multiple
components located on network
Communication over network is maintained by
passing messages
Three Tier Architecture
Distributed Processing
Components interact with each other to achieve
common goal
Processing is divided into multiple systems.
Processing power is increased
Three Tier Architecture
Three Tier Architecture
Example: Distributed Processing
Motivation is to share resources to increase
processing power
Non-Technical Example
The Battle Field
Three Tier Architecture
