Editing Thin client (section)

===Architecture===
In using cloud-based architecture, the server takes on the processing load of several client sessions, acting as a host for each endpoint device. The client software is narrowly purposed and lightweight; therefore, only the host server or server farm needs to be secured, rather than securing software installed on every endpoint device (although thin clients may still require basic security and strong authentication to prevent unauthorized access). One of the combined benefits of using cloud architecture with thin client desktops is that critical IT assets are centralized for better utilization of resources. Unused memory, bussing lanes, and processor cores within an individual user session, for example, can be leveraged for other active user sessions.

The simplicity of thin client hardware and software results in a very low [[total cost of ownership]], but some of these initial savings can be offset by the need for a more robust cloud infrastructure required on the server side.

An alternative to traditional server deployment which spreads out infrastructure costs over time is a cloud-based subscription model known as [[desktop as a service]], which allows IT organizations to outsource the cloud infrastructure to a third party.