Scribd
Upload
9 views

Lesson 01

information technology

Uploaded by

DK White Lion
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

Lesson 01

information technology

Uploaded by

DK White Lion
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

What is a Client?

• Any computer or program that makes a request to a


server

What is a Server?
• Any computer or program that processes the
requests of multiple computers or programs (clients)
• Typically, the server is always on and waits for client
requests
What is a Client-Server model?
• It is a software architecture model consisting of two
parts,
• client systems
• server systems
both communicating over a computer network or on
the same computer
Multitier Architecture
• In software engineering, multi-tier architecture (often referred
to as n-tier architecture) is a client–server architecture in which
• presentation
• application processing
• data management
functions are logically separated.
• The most widespread use of multi-tier architecture is the three-
tier architecture
• N-tier application architecture provides a model by which
developers can create flexible and reusable applications.
• By segregating an application into tiers, developers acquire the
option of modifying or adding a specific layer, instead of
reworking the entire application.
Three-tier Architecture
• Three-tier architectures typically comprise a
• presentation tier
• business or data access [logic] tier
• data tier
•
A Typical 3-tier Architecture

Presentation Layer
o Provides user interface
o Handles the interaction
with the user
o Sometimes called the
GUI or client view or
front-end
o Should not contain
business logic or data
access code
A Typical 3-tier Architecture
Logic Layer
o The set of rules for
processing information
o Can accommodate
many users
o Sometimes called
middleware/ back-end
o Should not contain
presentation or data
access code
A Typical 3-tier Architecture
Data Layer
o The physical storage
layer for data
persistence
o Manages access to
DB or file system
o Sometimes called
back-end
o Should not contain
presentation or
business logic code
Advantages of Three-tier Architecture
• The ability to separate logical components of an application
ensures that applications are easy to manage and understand.
i.e. experts can be employed that specialize in one of the layers e.g. user
interface design
• Communication can be controlled between each logical tier
Changes in one tier, for example, the database access tier, do not have to affect
the client component. i.e. a change from one DBMS to another would only
require a change to the component in the data access layer with little or no effect
on the business/logic (middle) or UI layer.
• Specific tools and technologies suited to each layer can be
deployed (and may evolve at a different pace).
• Components are reusable
• Faster development (division of work)
• Web designer does presentation
• Software engineer does logic
• DB admin does data model
Significance of “Tiers”

Database runs on Server


o Separated from client
o Easy to switch to a different database

Presentation and logic layers still tightly connected


o Heavy load on server
o Potential congestion on network
o Presentation still tied to business logic
Web oriented Three-tier Architecture
• Presentation tier
• Browser / custom client
• Client Side Scripting (JavaScript)
• Applets.
• Logical tier
• Web Server (Apache, IIS, Websphere etc.)
• Scripting Languages (PHP, Perl etc.)
• Programming Languages (Java, C, C# etc)
• Application Frameworks (Ruby on Rails etc.)
• Data tier
• Database Management System (DBMS) (Oracle, MySQL,
SQL Server, DB2 etc.)
• XMLDB
1-Tier Architecture

All 3 layers are on the same machine


o All code and processing kept on a single machine

Presentation, Logic, Data layers are tightly connected


o Scalability: Single processor means hard to increase volume
of processing
o Portability: Moving to a new machine may mean rewriting
everything
o Maintenance: Changing one layer requires changing other
layers
2-Tier Architecture

Database runs on Server


o Separated from client
o Easy to switch to a different database
Presentation and logic layers still tightly connected
(coupled)
o Heavy load on server
o Potential congestion on network
o Presentation still tied to business logic
3-Tier Architecture

o Each layer can potentially run on a different machine


o Presentation, logic, data layers disconnected
Questions?
Thank You

You might also like