Fat Client

Fat Client (English for fat client ) is a term used in electronic data processing and referred wholesome equipped, powerful desktop computer with sufficient computing capacity, hard disk, floppy disk and CD -ROM drives and powerful graphics cards. The counterpart to this is, depending on the application-specific functionality, the thin client.

In contrast to fat clients and thin clients that rich clients are ( sometimes referred to as smart clients referred to ) and provide a framework software solutions, application-specific functionality such as user interface, best performance, scale, and are directly from the client, for example, in desktop applications or on mobile platforms implemented.

During development of a client -server architecture, the term fat client is used for a desktop computer, in which the actual processing of the data is performed locally on the client. He also provides most of the graphical user interface.

The Fat Client consists of programming, hardware abstraction layer ( HAL) and the hardware itself A typical fat client, for example, a OS/2- or Windows-based personal computer ( PC) to be.

  • 4.2 Rich Client - platforms

Characteristics of a fat client

  • Data input and data output and data processing is done locally
  • The data storage is performed locally or on the network
  • Accessibility and communication in the network ( data services, mail server, firewall, etc.. )
  • A fat client (computer) usually involves moving parts ( eg. hard drive, fan)

Variants of a fat client

As an unmanaged PC ( locally managed PC with network access ) applying software installations and updates performed locally. All resources may, but need not, be used by the server and a server- free operation (offline ) is possible.

As a managed PC ( centrally managed PC with network access ) are software installations and updates recorded centrally. Management software such as eg. ZENworks or ZAK / SMS or SCCM is required and a server- free operation is possible temporarily.

Benefits

  • Less stringent requirements are placed on the particular server, as a fat client applications most self- processed and do not need to be swapped to a server
  • Increased possibility of working offline, as a dedicated connection to the server is often not required ( depending on application)
  • Relief for multimedia -rich application processors such as video gaming, as to the particular server no increased bandwidth demands must be made
  • It can be installed on the fat client even more applications, which already has an operating system on itself (local computer)
  • Increased server capacity, as each individual client ensures Fat for more processing, so that the respective server can thereby serve more clients.

Disadvantages

  • High administrative overhead, since modern operating systems are quite complex and incompatibilities with multiple revisions of the software used
  • With a high number of jobs is the delivery of applications to challenge, for example, when logon scripts or specific path information must be unified, as if the backend has been updated.
  • Vulnerability and loss, for example by visiting a Web page with malicious code intentionally or carelessly open an email attachment.
  • Providing a local administrator account, so even software can be installed, which poses security risks or changing, and deleting a configuration which can only be restored on site.

The thin client (hardware) as opposed

Thin Client is now used as a generic term for a variety of slim computers. For the operation of a thin client hardware less and less computing power is required. The features of thin clients is specified by several hardware manufacturers, and includes a minimum screen resolution of 640 × 480 pixels, a keyboard, a mouse, and the sound capability. Hard drives are not required but not explicitly excluded.

The operating system and the application software are central servers from which access occurs also program updates, and system administration. Thus, the system reliability is improved and the maintenance costs are lower. These include, for example, Windows-based terminals, network computers and NetPCs.

Definitions

Fat client ( hardware) - Here lies both the functionality and the application logic on the client itself This guarantees the client not only a high level of comfort for the user, but also by the offline capability a low dependence on a network.

Thin Client (hardware) - Is the opposite of a fat client. A thin client contains less hardware and no own application-specific functionality, this is completely provided by the server. The application-specific functions are usually represented here in the form of web pages.

Rich client (software ) - The Rich Client Platform (RCP ) is a framework for development of plug -in -based applications. Thus, a rich client not only solve a problem (like Fat Clients usual), but is also suitable for congeneric or even take in foreign issues. As an example may be mentioned here that a rich client, for example, not only read emails and mailing, but also can download and upload files via FTP.

Various frameworks are available today that offer a rich client platform (RCP ). These provide a basis in which the user 's Modules / Plug -ins ( troubleshooting ) can compose himself, he needs. Ideally, foreign solutions can work together (eg from different vendors ) within a rich client, appear so that all modules / plug- ins such as from a " cast ".

Software developers and suppliers to aggregate so-called rich client distributions from certain modules / plugins and provide specific user groups ready to help but even with these rich client platforms. A rich client has the advantage over a fat client that it is easier manageable and upgradable, for example, an automatic online update function in the client itself or a WebStarter that runs before the actual client.

Rich Client - Features

Here very briefly the usual must-have features of a Rich Client Platform:

  • Plugin- based adaptability to (different ) users ( requests)
  • Everything is really plug up to the application level (which is still ahead of the main window level) so that transform, various application - plugin the client to another application
  • Simple (online) updates the client or plug-ins
  • Development of complex surfaces for complex applications possible
  • Interdependent plugins (possibly differentiated in Kann-/Muss-Abhängigkeiten )
  • Config file management (either per Plugin own files or a central file)

In addition, there are sometimes outstanding Can properties:

  • Regardless of GUI frameworks (meaning it can use different or mix )
  • Next plugin manager also own event manager ( if, for example, regardless of GUI frameworks to bring the own event management )
  • Capable of running on different operating systems
  • Different surfaces on different devices
  • Addition to external and compiled-in plugins ( not only one of the two)
  • Updates / upgrades during operation ( without any tool by manually replacing all external plugins)

Rich Client - platforms

  • Eclipse RCP
  • NetBeans IDE
Desktop-Computer Client (computing) Bandwidth (signal processing) Software framework
327613
de