Thick and Thin client
The thick or thin client architecture is actually quite similar. In both cases, you can consider that it is the client application that runs on a PC whose function is to send and receive data through the network to the server program. The server would normally communicate that information to the medium-level software (the server), which retrieves and stores that information from a database.
Thick and Thin are the terms used to refer to the hardware (for example, how a PC communicates with the server), but the terms are also used to describe the applications. While this article deals specifically with hardware issues, be sure to check back as we will continue our Thick and Thin discussion related to the applications.
A thin client is designed to be especially small, so that most of the data processing occurs on the server. Although the term thin client often refers to software, it is increasingly used for computers, such as networked computers and networked PCs, which are designed to serve as clients for client / server architectures. A thin client is a networked computer without a hard drive. They act as a simple terminal for the server and require constant communication with the server as well.
Thin clients can be found in doctors’ offices, airline tickets, schools, governments, manufacturing plants and even call centers. In addition to being easy to install, thin clients also offer a lower total cost of ownership over heavy customers.
Thick Clients
In contrast, a thick client (also called a heavy client) is one that will do most of the processing in client / server applications. With heavy clients, there is no need for continuous communications with the server, since it is mainly about communicating file storage information to the server. As in the case of a thin client, the term is often used to refer to software, but it is also used to describe the networked computer. If your applications require multimedia components or that are bandwidth-intensive, you will also want to consider going with heavy clients. One of the biggest advantages of heavy clients lies in the nature of some operating systems and software that can not run on thin clients. Thick clients can handle this because they have their own resources.
Thick vs. thin – a comparison
Thin clients
- Easy to implement, since they do not require installation of additional or specialized software.
- You need to validate with the server after the data capture.
- If the server fails, the data collection stops as the client needs constant communication with the server
- Can not be interconnected with other equipment (for example, in factory installations or facilities)
- Clients run only and exactly as specified by the server
- More downtime
- The possibility that all applications are on the server so that any workstation can access.
- Opportunity to use old and obsolete PCs as clients
- Reduced security threat.
Thick Clients
- More expensive to implement and more work for IT implementation
- Data verified by non-server client (immediate validation)
- Robust technology provides better uptime
- You only need intermittent communication with the server
- More expensive to implement and more work for IT implementation
- They require more resources but fewer servers
- Can store local files and applications
- Reduction of server demands
- Increase in security problems
To get a best rpa training — RPA training in chennai | RPA training in bangalore | RPA training in pune | RPA online training | RPA interview questions and answers
Leave A Comment