A thin client refers to either a software program or to an actual computer that relies heavily on another computer to do most of its work. It operates as part of a network, with the client software or computer acting as an interface and the network server computer doing all the real work, like saving files, processing data, and controlling certain functions of the clients, like whether they can download things or not. This type of setup is commonly used in places with lots of people simultaneously using computers, like businesses or schools. Though this system is often easier to maintain and use, it also has some downsides, including the lack of peripherals and limited performance.
A physical thin client can be something as minimalistic as a graphic display and an input mechanism like a keyboard, mouse, or touchscreen. Generally speaking, these devices contain just enough information to start up and connect to a more powerful computer, the server. Many do not have the peripherals that come with personal computers like an optical drive or input/output ports, which are where wires connecting the computer to other devices come into it. They may also lack a hard drive, which means that if the client computer needs to use a program or save a file, it will connect to the network server computer to do so.
The software version is interface-based program. The user of the client software sees all of the data, tools, and features that would appear on a normal piece of software, but another program running on a remote server does the work.
Thin clients are typically used in settings where a lot of people need to use computers. This includes public places like libraries, airports, and schools. The thin client setup is also popular in places where people need to be able to save and access information from a central location, like an office, a call center, or a manufacturing plant. For instance, an office might use this type of setup to allow all employees to save all their work on an office server, or to control the programs and information that they can access.
The reasons someone might use hardware and software versions of a thin client include reduced cost, ease of maintenance, ease of use, and security. Thin clients are much more simple than complete computers, which means they may be less likely to break. A standard computer has a lot of parts, and a thin client only has a few — fewer parts mean fewer things can go wrong. The simplicity also makes it much easier to diagnose problems and repair them. Additionally, in a situation in which many people need to perform a similar task, it is often more cost-effective to have one network server computer and many cheap client computers than to have many complete devices.
People who are not computer literate may have an easier time using a thin client than a standard computer or software program because it has fewer features and functions to learn to use. Although thin clients are relatively easy to secure, users generally have restricted access to programs or functions that could breach security. Restricting all of the real computing power to a single network server also means that security can be focused in one place.
Downsides to this type of setup include the lack of peripheral devices, the limited performance of certain tasks, and sometimes, the nature of the security system. Those clients that don't have optical drives can't play CDs or DVDs, and if a client doesn't have input/output ports, it may be unable to easily connect to other devices, like a printer. Additionally, since most thin clients are so stripped down, their performance may not be fast enough for tasks like video rendering, graphics editing, or gaming. This is particularly true if several clients are doing very intensive tasks at once, which can affect the server and slow other clients down.
Though the ability to have one end point for all the security in a network can be beneficial, it also means that a problem with that one point can compromise all the client computers. Likewise, if none of the clients have hard drives and all the data is saved on the server, then if the server crashes, all the data from all the clients will be lost.