Search View Client/Server Architecture

To find a specific word, name, or topic in this article, select the option in your Web browser for finding within the page. In Internet Explorer, this option is under the Edit menu.

The search seeks the exact word or phrase that you type, so if you don’t find your choice, try searching for a key word in your topic or recheck the spelling of a word or name.

Client/Server Architecture

Client/Server Architecture, in computer science, an arrangement used on local area networks that makes use of “distributed intelligence” to treat both the server and the individual workstations as intelligent, programmable devices, thus exploiting the full computing power of each. This is done by splitting the processing of an application between two distinct components: a “front-end” client and a “back-end” server. The client component, itself a complete, stand-alone personal computer (versus the “dumb” terminal found in older architectures such as the time-sharing used on a mainframe) offers the user its full range of power and features for running applications. The server component, which can be another personal computer, minicomputer, or a mainframe, enhances the client component by providing the traditional strengths offered by minicomputers and mainframes in a time-sharing environment: data management, information sharing between clients, and sophisticated network administration and security features. The advantage of the client/server architecture over older architectures is that the client and server machines work together to accomplish the processing of the application being used. Not only does this increase the processing power available, but it also uses that power more efficiently. The client portion of the application is typically optimized for user interaction, whereas the server portion provides the centralized, multi-user functionality. See also Distributed Processing; Local Area Network.