What Is a Fat Client?

Rich client (Rich or Thick Client), as opposed to "Thin Client" (web-based application), is a feature-rich interactive user installed and configured on the client machine Interfaces, such as client management tools for Oracle and DB2 databases.

Rich client (Rich or Thick Client), as opposed to "Thin Client" (web-based application), is a feature-rich interactive user installed and configured on the client machine Interfaces, such as client management tools for Oracle and DB2 databases.

Chinese name

Fat client

Foreign name

Rich or Thick Client

Time

Mid 1990s

Field

computer

Relative

Thin client

Fat client mode

The application processing is divided into two parts: the processing performed by the user's desktop computer and the processing best performed by a centralized server. A typical thick client contains one or more applications running on the user's PC. The user can view and manipulate data, process some or all business rules-while providing a rich user interface to respond. The server is responsible for managing access to the data and is responsible for enforcing some or all business rules. There are also "variants" to this model that deal primarily with business rules and the physical location of the data. The point is that the thick client application runs on the user's computer.

Since the late 1990s, Web-based applications have been widely used, mainly because they can be easily used by end users, who need only a computer with Internet access. However, for highly interactive program interfaces, Web-based interfaces are difficult to meet the requirements. Writing complex client-side scripts that execute in an end-user browser is not a viable way to enhance interactivity. The business community recognizes that sometimes deploying a web-based solution will not meet all user needs. In addition, web-based applications cannot be used offline.

Fat Client Status

A fat client, sometimes called a thick client, is a network computer with rich resources installed locally, rather than spreading resources across the network like thin clients. For example, many PCs are personal clients because they have their own hard disks, CD / DVD drives, software applications, and so on.

Fat clients are always welcomed by network users, because fat clients can be customized, and users can choose what software to install and configure what special systems. On the other hand, thin clients are easy to manage, relatively easy to avoid security risks, and require no maintenance and licensing overhead. ^[1]

The current model is a fat client. A thick client is a client that runs lightweight components, and the user interface is responsible for these lightweight components. This application component works for the user, the external source requests the data, and then formats the data representation. That is, we see an application running on the iPhone. That's the model.

This model often prompts development to focus on the front end of SOA. It changes the focus of WS focus on development, and all the harsh problems are more REST style. ^[2]

Fat Client New Generation

Also called "smart client". It has made some changes to the fat user interface in the traditional client / server architecture since the mid-1990s. In traditional thick clients, users can easily and conveniently collect or The data displayed is interactive, which provides end users with high availability and efficiency. In addition, the smart client adds a web-based configuration, adding support for automatic version updates, online / offline operations, and managing client security in a controlled and secure manner.