Fat client
Fat Client is a term from electronic data processing and describes fully equipped, high-performance desktop computers with sufficient computing capacity, disk storage, CD-ROM drives and high-performance graphics cards. The counterpart to this is the thin client , depending on the application-specific functionality.
Unlike fat clients and thin clients that are rich clients (sometimes called smart clients referred to) and provide a framework - software solutions, application-specific functionality such as user interfaces, best performance , scale, and be directly at the client , such as desktop -applications or on mobile platforms implemented.
In the structure of a client-server architecture , the term fat client is used for a desktop computer on which the actual processing of the data is carried out on site on the client . It also mostly provides the graphical user interface.
The fat client consists of a programming interface , hardware abstraction layer (HAL) and the hardware itself. A typical fat client can be, for example, an OS / 2 or Windows- based personal computer (PC) .
Characteristics of a Fat Client
- Data input and data output as well as the data processing itself take place locally
- The data is stored locally or via the network
- Access options and communication via network (data services, mail server , firewall , etc.)
- A fat client (computer) often contains moving parts (e.g. hard drive , fan)
Variants of a fat client
As an unmanaged PC (locally managed PC with network access), software installations and updates are imported locally. All resources can, but do not have to, be used by the server and serverless operation ( offline ) is possible.
As a managed PC (centrally managed PC with network access) software installations and updates are imported centrally. Management software such as B. ZENworks or ZAK / SMS or SCCM is required and serverless operation is temporarily possible.
advantages
- Lower requirements can be placed on the respective server , since a fat client processes most of the applications itself and these do not have to be outsourced to a server
- Increased possibility of offline work , as a dedicated connection to the server (depending on the application) is often not required
- Relief for multimedia-rich application processing such as video gaming , since no increased bandwidth requirements have to be made on the respective server
- More applications can be installed on the fat client itself, since there is already an operating system on it (local computer )
- Higher server capacities, as each individual fat client provides more processing, so that the respective server can serve more clients .
disadvantage
- High administration effort, since modern operating systems are very complex and incompatibilities with different versions of the software used
- With a high number of workstations, the provision of applications becomes a challenge, for example when logon scripts or certain path information have to be standardized, for example when the back end has been updated.
- Vulnerability and resilience, for example by visiting a Web page with intentionally a defective code or carelessly open an attachment to an e-mail .
- Provision of a local administrator account, which allows you to install software yourself that involves security risks or changes and deletes a configuration that can only be restored on site.
The thin client ( hardware ) as a contrast
Thin client is used today as a generic term for a large number of slim computers. Less hardware and less computing power are required tooperate a thin client . The equipment of thin clients isspecifiedby several hardware manufacturers and includes a screen resolution of at least 640 × 480 pixels, a keyboard , a mouse and sound capability. Hard disks are not required but also not explicitly excluded.
The operating system and the application software are located on central servers from which program updates and system administration are also carried out. As a result, system reliability is better and maintenance costs are lower. These include B. Windows terminals , network computers and NetPCs .
Definitions
Fat Client ( Hardware ) - Both the functionality and the application logic lie with the client itself. This guarantees the client not only a high level of convenience for the user, but also, thanks to the offline capability, less dependence on a network .
Thin Client ( Hardware ) - Is the exact opposite of a fat client . A thin client contains less hardware and no application-specific functionality of its own; this is completely provided by the server . The application-specific functions are usually in the form of this web illustrated pages.
Rich Client ( Software ) - The Rich Client Platform ( RCP ) is a framework for developing plug-in- based applications. A rich client can not only solve a problem (as isusualwith fat clients ), but is also suitable for related or even alien problems. As an example, it should be mentioned here that a rich client z. B. can not onlyread and send e-mails , but alsodownload and uploadfiles via FTP .
Various frameworks are available today that offer a rich client platform ( RCP ). These provide a basis in which the user can put together the modules / plug-ins (problem solutions) that he needs. Ideally, third-party solutions (e.g. from different providers) can work together within a rich client , so that all modules / plug-ins appear as if they were "cast from a single source".
Software developers and providers can also use these rich client platforms tobundleso-called rich client distributions from specific modules / plugins and make them available to specific user groups. A rich client has the advantage over a fat client that it is easier to manage and update, for example through an automatic online update function in the client itself or a WebStarter that isexecutedbefore the actual client .
Rich client properties
Here are the usual must-have properties of a rich client platform:
- plugin-based adaptability to (different) users (requirements)
- really everything is plug-in right down to the application level (which is before the main window level), so that various application plug-ins can transform the client into another application
- simple (online) updates of the client or plugins
- Development of complex surfaces for complex applications possible
- interdependent plugins (possibly differentiated into optional / must dependencies)
- Config file management (either separate files for each plugin or a central file)
In addition, there are sometimes outstanding can properties:
- independent of GUI frameworks (so can use or mix different ones)
- In addition to the plug-in manager, also their own event manager (if e.g. independent of GUI frameworks that bring their own event management)
- executable under different operating systems
- different surfaces on different devices
- in addition to external and compiled plugins (not just one of the two)
- Updates / upgrades during operation (possibly without a tool by manually replacing external plugins)
Rich client platforms
See also
Individual evidence
- ↑ IT Knowledge - Online Lexicon - Der Fat Client accessed on December 30, 2013
- ↑ Technopedia - Hardware - Fat Client - English , accessed on December 30, 2013.
- ↑ BSK Service GmbH - The classic desktop PC accessed on December 30, 2013
- ↑ IT Knowledge - Online Lexicon - Thin Client accessed on December 30, 2013