Their purposes and application may vary, but the basic architecture remains the same.
This technology description provides a summary of some common client/server architectures and, for completeness, also summarizes mainframe and file sharing architectures. Detailed descriptions for many of the individual architectures are provided elsewhere in the document. (Fastie 1999)
Although this idea is applied in a variety of ways, on many different kinds of applications, the easiest example to visualize is the current use of web pages on the Internet. For example, if someone read a Web page, his computer and web browser is considered a client, and the computers, databases, and applications that make up the Web page are considered the server.
The term client/server was first used in the 1980s in reference to personal computers (PCs) on a network. The actual client/server model started gaining acceptance in the late 1980s. The client/server software architecture is a versatile, message-based and modular infrastructure that is intended to improve usability, flexibility, interoperability, and scalability as compared to centralized, mainframe, time sharing computing.
In the late 1980s, the actual client/server model started gaining acceptance. ...
Client/server architecture illustrates the relationship between two computer programs in which one program is a client, which makes a service request to another program called as Server. Server provides service to the request. A single machine can be act as both, a client as well as server depending on the software configuration. Although the client/server architecture can be used within a single computer by programs, but it is a more important idea in a network. In a network, the client/server architecture allows efficient way to interconnect programs that are distributed efficiently across different locations. The common use of client/server model is in Computer transactions. For example, if you have to check a bank account from your computer, you have to send a request to a server program at the bank. That program process the request and forward the request to its own client program that sends a request to a database server at another bank computer to retrieve client balance information. The balance is sent back to the bank data client, which in turn serves it back to your personal computer, which displays the information of balance on your computer. (Jorvekar 2005)
Goodyear (1999) defines client/server computing as a style of computing that involves multiple processors, one of which is typically a workstation and across which a single business transaction is completed. Also he mentions the term "netcentric", which is actually a shortened version of "network centric". Client/server computing recognized that business users, and not a mainframe, were the real center of a business. Therefore, client/server was also "client-centric" computing. Today the concept of