Scribd
Upload
4 views14 pages

M1L2V1 Evolution

The document discusses the evolution of web application architectures, focusing on layered patterns that separate concerns for better modularity and maintainability. It outlines various architectures including two-layer systems, three-tier architectures, and n-tier web applications, emphasizing the importance of clear separation of logic between presentation and business layers. Additionally, it highlights the characteristics of service-based web applications and the role of third-party APIs.

Uploaded by

2024sl93009
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4 views14 pages

M1L2V1 Evolution

The document discusses the evolution of web application architectures, focusing on layered patterns that separate concerns for better modularity and maintainability. It outlines various architectures including two-layer systems, three-tier architectures, and n-tier web applications, emphasizing the importance of clear separation of logic between presentation and business layers. Additionally, it highlights the characteristics of service-based web applications and the role of third-party APIs.

Uploaded by

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

Full Stack Application Development

Application Development- Introduction


Web application architectures
Akshaya Ganesan
Evolution of Web application
architectures
Learning Outcomes:
At the end of this video, you will be able to:

• Evolution of Web application architectures

Faculty
Layered Pattern
Context: Separation of concern

Problem: Modules of the system may be independently


developed and maintained, supporting portability,
modifiability, and reuse.

Solution: The layered pattern divides the software into units


called layers.

Each layer is a grouping of modules that offers a cohesive Faculty


set of services.

Each partition is exposed through a interface.

Layers interact according to a strict ordering relation and


unidirectional.
Web Application
• Web application follows the Layered Architecture.
• Two-layer systems
• Typical client-server system
• The client held the user interface and other
application code, and the server was usually a
relational database.
• Embed the logic directly into the UI screens
• Alternative: put the domain logic in the database
Faculty
as stored procedures.
3-Tier Architecture
• A typical Web Application:

Presentation (UI)

Business Logic

Data Access Faculty


Traditional Web Application
Three Tier

Business
Logic
HTML CSS JS

Client(Browser) Web Server

Presentation Static
Logic content

Client Tier Internet Server Tier Data Tier


Ensuring a clear separation of concern
• Scenario 1: A list of products in which all the products
that sold over 10 percent more than they did the
previous month were coloured in red.
• Method 1: (putting domain logic into the
presentation)
• Developers placed logic in the presentation layer
that compared this month’s sales to last month’s
sales, and if the difference was more than 10
percent, they set the colour to red.
Faculty
Ensuring a clear separation of concern
• Scenario 1: A list of products in which all the products
that sold over 10 percent more than they did the
previous month were coloured in red.
• Method 2: To properly separate the layers, you
need a method in the domain layer to indicate if a
product has improved sales. This method makes
the comparison between the two months and
returns a Boolean value.
• The presentation layer then calls this Boolean
method and, if true, highlights the product in red. Faculty
Ensuring a clear separation of concern
• Scenario 2:You need to add different layers to an
application, such as a command-line interface to a
Web application.
• Method: If there’s any functionality you have to
duplicate to do this, that’s a sign of where domain
logic has leaked into the presentation
• Similarly, do you have to duplicate logic to replace
a relational database with an XML file?

Faculty
N-Tier Web Application

Client(Browser)

Internet Application
Client(Browser) Web Server DB
Server

HTML CSS JS
Client(Browser)

Client Tier Internet Server Tier Business Tier Data Tier


Characteristics

Each tier is completely independent.

The nth tier only has to know how to handle a request


from the n+1th tier

Tiers make it easier to ensure security and to optimize


performance and availability in specialized ways.

Faculty
Service Based Web Application

Third Party
APIs

Client(Browser)

Internet Application
Client(Browser) Web Server DB
Server

HTML CSS JS
Client(Browser) REST API DB

Client Tier Internet Server Tier Business Tier Data Tier


Summary
In this video, you have learned about:

• Evolution of Web Applications

Faculty
Thank You!

You might also like