Fat Client

Fat Clients and Servers. Please respond to the following: Provide a scenario in which the use of fat servers would be preferred over the use of fat clients. Describe why fat servers, rather than fat clients, should be used in your scenario. Compare the pros and cons of Intranets to those of the Internet from an organizational perspective. Suggest one way to integrate the two and the benefits this may bring. Fat Client A user's computer that contains its own applications that are run in the machine. New programs are installed on the local hard disk. This is the typical way people use their computers. A fat client is : Fat clients are the more traditional form of client/server. The bulk of the application runs on the client side of the equation. 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. They provide flexibility and opportunities for creating front-end tools that let end-users create their own applications. Fat Server: A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client. A fat server also: 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. Transaction and object servers, for example, encapsulate the database. The client in the fat server model provides the GUI and interacts with the server through remote procedure calls (or method invocations) These are used for mission-critical applications, represent the new growth area fro PC-based client/server computing. Here is an article that I found shows justification why Fat server are beneficial than Fat Clients. IDG News Service - Adjusting to changes in corporate hardware buying...