Difference : ->
Thin client are also known as x terminalsA thin client,
sometimes also called a lean client, is a computer (client) in client-server architecture networks which depends primarily on the central server for processing activities. The word "thin" refers to the small boot image which such clients typically require - perhaps no more than required to connect to a network and start up a dedicated web browser or "Remote Desktop" connection such as X11, Citrix ICA, Microsoft RDP or Nomachine NX.
In contrast, a thick or fat client does as much processing as possible and passes only data required for communications and archival storage to the server.
Which one work Better : ->
It Depends on u'r need though i tell u the advantages of both now u decide which one suits u'r budget as well as u'r interest:
Advantage thin client=>
Obviously, boot image control is much simpler when only thin clients are used - typically a single boot image can accommodate a very wide range of user needs, and be managed centrally, resulting in:
* Lower IT admin costs. Thin clients are managed almost entirely at the server. The hardware has fewer points of failure and the local environment is highly restricted (and often stateless), providing protection from malware.
* Easier to secure. Thin clients can be designed so that no application data ever resides on the client (it is entirely rendered), centralizing malware protection.
* Lower hardware costs. Thin client hardware is generally cheaper because it does not contain a disk, application memory, or a powerful processor. They also generally have a longer period before requiring an upgrade or becoming obsolete. The total hardware requirements for a thin client system (including both servers and clients) are usually much lower compared to a system with fat clients. One reason for this is that the hardware is better utilized. A CPU in a fat workstation is idle most of the time. With thin clients, memory can be shared. If several users are running the same application, it only needs to be loaded into RAM once with a central server. With fat clients, each workstation must have its own copy of the program in memory.
* Lower Energy Consumption. Dedicated thin client hardware has much lower energy consumption than thick client PCs. This not only reduces energy costs but may mean that in some cases air-conditioning systems are not required or need not be upgraded which can be a significant cost saving and contribute to achieving energy saving targets.
* Worthless to most thieves. Thin client hardware, whether dedicated or simply older hardware that has been repurposed via cascading, is useless outside a client-server environment. Burglars interested in computer equipment have a much harder time fencing thin client hardware (and it is less valuable).
* Hostile Environments. Most devices have no moving parts so can be used in dusty environments without the worry of PC fans clogging up and overheating and burning out the PC.
* Less network bandwidth. Since terminal servers typically reside on the same high-speed network backbone as file servers, most network traffic is confined to the server room. In a fat client environment if you open a 10MB document that's 10MB transferred from the file server to your PC. When you save it that's another 10MB from your PC to the server. When you print it the same happens again - another 10MB over the network to your file server and another 10MB back to the printer. This is highly inefficient. In a thin client environment only mouse movements, keystrokes and screen updates are transmitted from/to the end user. Over efficient protocols such as ICA or NX this can consume as little as 5Kbps bandwidth.
* More efficient use of resources. A typical thick-client will be specified to cope with the maximum load the user needs, which can be inefficient at times when it is not utilised. In contrast, thin clients only use the exact amount of resources required by the current task - in a large network, there is a good probability the load from each user will fluctuate in a different cycle to that of another user (i.e. the peaks of one will more than likely correspond, time-wise, to the troughs of another.
* Simple hardware upgrade path. If the peak resource usage is above a pre-defined limit, it is a relatively simple process to add another rack to a blade server (be it power, processing, storage), boosting resources to exactly the amount required. The existing units can be continued in service alongside the new, whereas a thick client model requires an entire desktop unit be replaced, resulting in down-time for the user, and the problem of disposing of the old unit.
Advantage thick client =>
* Fewer server requirements. A thick client server does not require as high a level of performance as a thin client server (since the thick clients themselves do much of the application processing). This results in drastically cheaper servers.
* Better multimedia performance. Thick clients have advantages in multimedia-rich applications that would be bandwidth intensive if fully served. For example, thick clients are well suited for video gaming.
* More flexibility. On some operating systems (such as Microsoft Windows) software products are designed for personal computers that have their own local resources. Trying to run this software in a thin client environment can be difficult.