You are on page 1of 15

3-Tier Client/Server Architecture

Background
Demand enterprise-class applications Partitioning of applications
2-Tier, 3-Tier, N-Tier

What are these Tiers ?


Physical partitioning of applications
terminal(tier1), minicomputer(tier2), mainframes(tier3)

Logical partitioning of applications


2-tier
client(tier 1) :a big chunk of application server(tier 2) : DBMS

3-tier
client(tier1) : GUI application server(tier2) : all chunk of business applications server(tier3) : DBMS

Tier 1
SQL, File Server, HTTP protocol

Tier 2

GUI
A 2-Tier Client-Server Application Architecture Database(or Other Resource Managers)

Tier 1
GUI

Tier 2

Tier 3

Application RPCs, Conversations, Queues, Publish-and-Subscribe, Broadcasts, Object invocations A 3-Tier Client-Server Application Architecture

Database(or Other Resource Managers)

Why 3-Tier Architecture ?


Reasons
Meets the requirements of large-scale internet and intranet client/server applications Is easier to manage and deploy on the network
most of code runs on the servers, especially technologies like Java applets

Minimizes network interchanges by creating abstract levels of service Provides better security
by not exposing the database schema to the client by enabling more fine-grained authorization on the server

Three Tiers
The key to using Remote Data Service technology lies in understanding the three-tiered client/server model. This approach separates the various components of a client/server system into three "tiers": Client Tier Middle Tier

Data source Tier

3-tier architecture

Arch(cont..)

Client tier
A local computer on which either a Web browser displays a Web page that can display and manipulate data from a remote data source, or (in non-Web-based applications) a stand-alone compiled front-end application.

Middle tier
A Server computer that hosts components which encapsulate an organization's business rules. Middle-tier components can either be Active Server Page scripts executed on Internet Information Server, or (in non-Web-based applications) compiled executables.

Data source tier


A computer hosting a database management system (DBMS), such as a Microsoft SQL Server database. (In a two-tierapplication , the middle-tier and data source tier are combined.)

Advantages
Removes a huge processing burden from client machines. Can be used to consolidate enterprise-wide business rules as application servers process business rules in a single place for use by multiple applications. When rules change, only a change to the application server is required. Any knowledge of the database server may be hidden from the client. Database queries may be presented to client in alternative forms.

Cost to Develop and Maintain

2-Tier Architecture

3-Tier Architecture

Application Complexity and Length of Application Life

Conclusion
It has become a safe bet to implement your applications using a 3-tier client/server Architecture

It supports - security - reusability - step-wise, add-on, and customized integration - etc

You might also like