Client/server applications can also be differentiated based on how the application is split between the client and the server. The fat ser...
Client/server applications can also be differentiated based on how the application is split between the client and the server. The fat server model places more function on the server and the fat client model places more functions on the clients. Groupware, transaction and web servers are fat servers and file servers are example for fat clients.
Fat clients are the most traditional form of client/server. In both the file server and database server models, the clients know how the data is organized and stored on the server side. Fat clients are used for decision support and personal software.
Fat server applications are easier to manage and deploy on the network because most of the code runs on the servers. Fat servers try to minimize network interchanges by creating more abstract levels of service. Instead of exporting raw data, they export the procedures that operate on the data. The client in the fat server model interacts with the server using RPC (Remote Procedure Calls).
2 Tier versus 3 Tier:
This is about splitting the client/server applications into functional units that can be assigned to either clients or servers. The most typical functional units are the user interface, the business logic and the shared data.
In 2-tier client/server architecture, the application logic is either buried inside the user interface on the client or within the database on the server.
In a 3 tier client/server architecture, the application logic lives in the middle tier. It is separated from the user interface and the data. 3-tier systems are more scalable, robust and flexible. In addition they can integrate data from multiple sources. Examples of 3-tier systems are TP Monitors, distributed objects and the web.
Fat clients are the most traditional form of client/server. In both the file server and database server models, the clients know how the data is organized and stored on the server side. Fat clients are used for decision support and personal software.
Fat server applications are easier to manage and deploy on the network because most of the code runs on the servers. Fat servers try to minimize network interchanges by creating more abstract levels of service. Instead of exporting raw data, they export the procedures that operate on the data. The client in the fat server model interacts with the server using RPC (Remote Procedure Calls).
2 Tier versus 3 Tier:
This is about splitting the client/server applications into functional units that can be assigned to either clients or servers. The most typical functional units are the user interface, the business logic and the shared data.
In 2-tier client/server architecture, the application logic is either buried inside the user interface on the client or within the database on the server.
In a 3 tier client/server architecture, the application logic lives in the middle tier. It is separated from the user interface and the data. 3-tier systems are more scalable, robust and flexible. In addition they can integrate data from multiple sources. Examples of 3-tier systems are TP Monitors, distributed objects and the web.
