Client/Server Computing

Also found in: Acronyms.
An information system architecture in which one or more dedicated servers process requests from peripheral computers, acting as a buffer among peripheral ‘nodes’
References in periodicals archive ?
However, a key step in the survival process for implementing client/server computing is understanding how much it will cost.
These costs are well-understood for mainframe applications, but they often are overlooked and nearly always underestimated when planning for client/server computing.
The cultural issues of client/server computing, for example, are just as complex as the technical issues.
The cost of migrating to client/server computing can be significant--and not just for the new applications development.
No one has defined a standard approach to this, yet it needs to be done consistently throughout an enterprise to reap the full benefits of client/server computing.
Despite these costs and management challenges, it may be more expensive not to embrace client/server computing.
Ideally, client/server computing gives you the responsiveness, familiarity and ease-of-use benefits of PCs with the performance, reliability, data integrity and security of the mainframe, coupled with the ability to support many users simultaneously.
Client/server computing evolved from the limitations of early LANs which used PCs as shared, centralized file servers.
The next step towards client/server computing is to divide the application, putting part of it on the user's computer, the client, and the rest on the server.