database

Client/Server Architecture for DBMS

Client/Server Computing represents a model wherein requests are made at one end & the client end and provided at another server end.
A client is defined as a requester of services & Server is defined as the provider of services. A single machine can be both client/server prog. architecture.

One-Tier Computing Model 

Two Tier Computing Model

 

                                               Client <==============================> Server

Traditional database client/server architecture is based on 2 Tier computing model. This Model consists of a client tier and a database server tier.
Processing tasks and application logic are shared b/w database server & client.
Disadvantage
The client in 2-Tier are fat client( application responsible for its processing power & app. logic).
This makes the clients costly to maintain. Clients can be operated on diff. platforms, results in the deployment of platform specific versions of applications.

Three Tier Computing Model

                                   Client <=============> Middle Tier <====================> Server

To overcome the 2-Tier computing model disadvantages, 3-Tier computing model was introduced ( A middle tier exists b/w clients and the database server). The middle tier consists of an application server that contains the bulk of application logic. Clients in this model are thin clients.
Thin Clients: Application that does not have much of processing power or application logic, rather it provides a User Interface(UI) only.
As the middle tier in a three-tier architecture, the application provides the optimal interface b/w clients and database. It supports the deployment of distributed component applications based on CORBA(Common Object Request Broker Architecture) standard.
SHARE
Previous articleDBMS vs FPS
Next articleDatabase Transaction
avatar

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  Subscribe  
Notify of