Exponential
Technologies Solutions |
 |
Client/Server
Solutions / Web-Based
Solutions / Network Design &
Implementation /
Training |
 |
 |
Client/Server Solutions |
 |
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. A client is defined as a
requester of services and a server is defined as the provider of
services. A single machine can be both a client and a server
depending on the software configuration.
As a result of the limitations of file sharing
architectures, the client/server architecture emerged. This approach
introduced a database server to replace the file server. Using a
relational database management system (DBMS), user queries could be
answered directly. The client/server architecture reduced network
traffic by providing a query response rather than total file
transfer. It improves multi-user updating through a GUI front end to
a shared database. In client/server architectures,
Remote Procedure Calls (RPCs) or standard query language (SQL) statements are typically used to communicate between the
client and server.
|
 |
Two-Tier Architecture
:: Good solution for distributed computing when work groups are defined as a
dozen to 100 people interacting on a LAN simultaneously. Limitations include: 1) performance degradation
when over 100 users due to server maintaining a connection via "keep-alive"
messages with each client, even when no work is being
done; 2) limited flexibility in moving (repartitioning)
program functionality from one server to another without manually
regenerating procedural code. |
 |
Three-Tier (N-Tier)
Architecture
:: A middle tier (e.g. transaction processing monitor, message
server, application server) is added between the user
system interface client environment and the database management
server environment. The middle tier can perform message queuing, application execution,
and/or database staging. Using this approach has been shown to improve performance for groups
with a large number of users (in the thousands) and
improves flexibility when compared to the two tier approach. |
 |
|
 |
|
 |
|
 |
top of page |
 | |
|