Scribd
Upload
26 views

Web App Architectures - N Tiers

The document discusses web app architectures, focusing on multi-tier (2-tier and 3-tier) architectures. It describes how multi-tier architectures separate an application into presentation, business/logic, and data tiers that can each run on separate machines. This allows each tier to be developed and scaled independently. A typical 3-tier architecture has a presentation tier for the front-end, a logic/business tier for processing in the middleware, and a data tier for the database backend.

Uploaded by

a82503123
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
26 views

Web App Architectures - N Tiers

The document discusses web app architectures, focusing on multi-tier (2-tier and 3-tier) architectures. It describes how multi-tier architectures separate an application into presentation, business/logic, and data tiers that can each run on separate machines. This allows each tier to be developed and scaled independently. A typical 3-tier architecture has a presentation tier for the front-end, a logic/business tier for processing in the middleware, and a data tier for the database backend.

Uploaded by

a82503123
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/ 11

Web App Architectures

MULTI-TIER (2-TIER, 3-TIER)


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
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
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
3-Tier Architecture

● Each layer can potentially run on a different machine


● Presentation, logic, data layers disconnected
A Typical 3-tier Architecture
Architecture Principles
● Client-server architecture
● Each tier (Presentation, Logic, Data)
should be independent and should
not expose dependencies related
to the implementation
● Unconnected tiers should not
communicate
● Change in platform affects only the
layer running on that particular
platform
A Typical 3-tier Architecture
Presentation Layer
● Provides user interface
● Handles the interaction with
the user
● Sometimes called the GUI or
client view or front-end
● Should not contain business
logic or data access code
A Typical 3-tier Architecture
Logic/Business Layer
● The set of rules for processing
information
● Can accommodate many
users
● Sometimes called
middleware/back-end
● Should not contain
presentation or data access
code
A Typical 3-tier Architecture
Data Layer
● The physical storage layer for
data persistence
● Manages access to DB or file
system
● Sometimes called back-end
● Should not contain
presentation or business logic
code
The 3-Tier Architecture for Web Apps (Summary)

● Presentation
○ Layer Static or dynamically generated content rendered by the browser
(front-end)
● Logic/Business Layer
○ A dynamic content processing and generation level application server, e.g.,
Java EE, ASP.NET, PHP, ColdFusion platform (middleware)
● Data Layer
○ A database, comprising both data sets and the database management system
or RDBMS software that manages and provides access to the data (back-end)
The 3-Tier Architecture - Advantages

● Independence of Layers
○ Easier to maintain
○ Components are reusable
○ Faster development (division of work)
■ Web designer does presentation
■ Software engineer does logic
■ DB admin does data model

You might also like