2020Auerbach Publications eBooksRequires access

Client/Server Architecture and Implementation

Nathan J. Muller

Open publisher page 0 citations

Abstract

In the client/server model, an application program is broken out into two parts on the network. The client portion of the program, or front end, is run by individual users at their desktops and performs such tasks as querying a database, producing a printed report, or entering a new record. The server portion of the program, or back end, resides on a computer configured to support multiple clients, offering them shared access to a variety of application programs as well as to printers, file storage, database management, communications, and other resources. The migration from central to distributed computing has produced two types of networks involving server: the traditional hierarchical architecture employed by mainframe vendors and the distributed architecture employed by local area networks. Those who have taken the plunge into client/server applications have noted that their organizations are becoming increasingly dependent on enterprise networks. Companies spend $20 million annually in network support.

About this research paper

What this paper is about

In the client/server model, an application program is broken out into two parts on the network. The client portion of the program, or front end, is run by individual users at their desktops and performs such tasks as querying a database, producing a printed report, or entering a new record. The server portion of the program, or back end, resides on a computer configured to support multiple clients, offering them shared access to a variety of application programs as well as to printers, file storage, database management, communications, and other resources. The migration from central to distributed computing has produced two types of networks involving server: the traditional hierarchical architecture employed by mainframe vendors and the distributed architecture employed by local area networks. Those who have taken the plunge into client/server applications have noted that their organizations are becoming increasingly dependent on enterprise networks. Companies spend $20 million annually in network support.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

In the client/server model, an application program is broken out into two parts on the network. The client portion of the program, or front end, is run by individual users at their desktops and performs such tasks as querying a database, producing a printed report, or entering a new record. The server portion of the program, or back end, resides on a computer configured to support multiple clients, offering them shared access to a variety of application programs as well as to printers, file storage, database management, communications, and other resources. The migration from central to distributed computing has produced two types of networks involving server: the traditional hierarchical architecture employed by mainframe vendors and the distributed architecture employed by local area networks. Those who have taken the plunge into client/server applications have noted that their organizations are becoming increasingly dependent on enterprise networks. Companies spend $20 million annually in network support.

Key concepts: Computer science, Architecture, Operating system, Client–server model, Computer network, Computer architecture, Server, History

Related papers

Back to paper searchBrowse research topicsOriginal source
Client/Server Architecture and Implementation — Research Paper | ScholarLens