2tier -> DB Server <-data-> Client
3tier -> DB Server <-data-> Service tier <-results/inputs-> Client
In 2 tier all needed data from DB are sent to the client which process them.
In 3 tier, client sends "only" some request for data, service tier read data from DB server, process them and only the requested result is sent to the client.
It means the Processing and Presentation is separated and it means that data processing can run on some fast HW (server) and client is "just" displaying the results and collect user inputs (and make all needed actions which are needed to display the data etc.).
In 2 tier system all raw data from DB must be transfered to the Client which will process them and display them.
This is the "basic" difference. Of course, take it as an example without details and things around...
Comments
3tier -> DB Server <-data-> Service tier <-results/inputs-> Client
In 2 tier all needed data from DB are sent to the client which process them.
In 3 tier, client sends "only" some request for data, service tier read data from DB server, process them and only the requested result is sent to the client.
It means the Processing and Presentation is separated and it means that data processing can run on some fast HW (server) and client is "just" displaying the results and collect user inputs (and make all needed actions which are needed to display the data etc.).
In 2 tier system all raw data from DB must be transfered to the Client which will process them and display them.
This is the "basic" difference. Of course, take it as an example without details and things around...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!