Client/Server computing is new technology that yields solutions to many data management problems

faced by modern organizations (MIS Terminology).

Client/Server is used to describe a computing model for the development of computerized systems.

This model is based on distribution of functions between two types of independent and autonomous
processes: Server and Client

A Client is any process that services from the server process.

A Server is a process that provides requested services for the Client.

1.1.1 A Server for Every Client

A file server can store any type of data, and so on simpler systems, may be the only server necessary.

Different types of servers

1. File Server
All the files reside on the server machine. File Server provides clients access to records within
files from the server machine. File Servers are useful for sharing files across a network among
the different client process requesting the services.

2. Print Server
This machine manages user access to the shared output devices, such as printers. These are the
earliest type of servers. Print services can run on a file server or on one or more separate print
server machines.

3. Application Server

This machine manages access to centralized application software; for example, a shared
database. When the user requests information from the database, the application server
processes the request and returns the result of the process to the user.

4. Mail Server
This machine manages the flow of electronic mail, messaging, and communication with
mainframe systems on large-scale networks.

5. Fax Server
Provides the facility to send and receive the Faxes through a single network connection. The Fax
server can be a workstation with an installed FAX board and special software or a specialized
device dedicated and designed for Fax Services.

6. Directory Services Server

It is found on large-scale systems with data that is distributed throughout multiple servers. This
machine functions as an organization manager, keeping track of what is stored where, enabling
fast and reliable access to data in various locations.
 7. Web Server
This machine stores and retrieves Internet (and intranet) data for the enterprise. Some
documents, data, etc., reside on web servers

8. Database Server
Data resides on server, in the form of a SQL database. Database server provides access to data to
clients, in response to SQL requests. It shares the data residing in a database across a network.

9. Transaction Servers
The data and remote procedures reside on the server. The Server provides access to high level
functions, and implements efficient transaction processing. It shares data and high level
functions across a network.

10. Groupware Servers

Liable to store semi-structured information like text, image, mail, bulletin boards, flow of work.
Groupware Server provides services, which put people in contact with other people, that is
because groupware” is an ill-defined classification protocol differing from product to product.

11. Object Application Servers

Communicating distributed objects reside on the server. The object server primarily provides
access to those objects from the designated client objects. The object Application Servers are
responsible for sharing distributed objects across the network.

1.1.2 Client/Server: Fat or Thin

thin client is one that conducts a minimum of processing on the client side

fat client is one that carries a relatively larger proportion of processing load

Fat Clients: This architecture places more application functionality on the client machine(s). They are
used in traditional of Client/Server models.

Fat Servers: This architecture places more application functionality on the server machine(s). Typically,
the server provides more abstract, higher- level services.

A stateless server is a server that treats each request as an independent transaction that is unrelated to
any previous request.

A stateless server keeps no state information. Using a stateless file server, the client must specify
complete file names in each request specify location for reading or writing and re-authenticate for each
request

A stateful server remembers client data (state) from one request to the next.
1.1.4 Servers and Mainframes
Mainframes are the monstrous computer system that deals mainly the business functions and
technically these giant machines will run MVS, IMS and VSAM operating systems

Various other factors, which can have, prime considerations to differentiate themainframe and
Client/Server systems:

 Application development: Mainframe systems are over structured, time-consuming and

create application backlogs.
 Data manipulation: Mainframe systems have very limited data manipulation capabilities
whereas these techniques are very flexible in the case of Client/Server systems
 System management: Mainframe systems are known to be integrated systems but in the
case of Client/Server systems only few tools are available for system management.
 Security: Mainframe systems are highly centralized whether as Client/Server systems are
relaxed or decentralized.
 End user platform: Mainframe systems comprise of dumb terminals, are character
based, single task oriented and of limited productivity

Client/Server Functions

The main operations of the client system are listed below:

• Managing the user interface.
• Accepts and checks the syntax of user inputs.
• Processes application logic.
• Generates database request and transmits to server.
• Passes response back to server.

The main operations of the server are listed below:

• Accepts and processes database requests from client.
• Checks authorization.
• Ensures that integrity constraints are not violated.
• Performs query/update processing and transmits responses to client.
• Maintains system catalogue.
• Provide concurrent database access.
• Provides recovery control

1.1.6 Client/Server Topologies

A Client/Server topology refers to the physical layout of the Client/Server network in which all the
clients and servers are connected to each other.
  Single client, single server: This topology is shown in the Fig. 1.2 given below. In this
topology, one client is directly connected to one server.
 Multiple clients, single server: This topology is shown in the Fig. 1.3 given below. In this
topology, several clients are directly connected to only one server.
 Multiple clients, multiple servers: This topology is shown in the following Fig. 1.4 In this
topology several clients are connected to several servers.

1.1.7 Integration with Distributed Computing

Distributed computing is the term used for implementation of technologies across heterogeneous
environments

1.2 CLASSIFICATION OF CLIENT/SERVER SYSTEMS

1. First-tier (client-tier): The main responsibility of this tier is to receive user events and to control
the user interface and presentation of data.
2. Second-tier (application-server-tier): The complex application logic is loaded here and available
to the client tier on request from client
3. Three-tier (database-server-tier): This tier is responsible for data storage. This server mostly
operates on a relational database

1.2.2.1 Transaction Processing Monitors

A Transaction Processing Monitor is a program that controls data transfer between client and server in
order to provide consistent environment, particularly for online transaction processing (OLTP).

Transaction Routing: TP monitor can increase scalability by directing transactions to specific DBMS’s.

Managing Distributed Transaction: The TP Monitor can manage transactions that require access to data
held in multiple, possibly heterogeneous, DBMSs.

Load balancing: The TP Monitor can balance client requests across multiple DBMS’s on one or more
computers by directing client services calls to the least loaded server.

Funneling: In an environment with a large number of users, it may sometimes be difficult for all users to
be logged on simultaneously to the DBMS.

Increased reliability: The TP Monitor acts as transaction manager, performing the necessary action to
maintain the consistency of database, with the DBMS acting as a resource manager.
A TP Monitor is typically used in environments with a very heavy volume of transaction, where the TP
Monitor can be used to offload processes from the DBMS server

Messaging is another way to implement the three-tier architecture.

N-tier computing obliges developer to design components according to a business schema that
represents entities, relationship, activities roles, and rules, thereby enabling them to distribute
functionality across logical and physical tiers, allowing better utilization of hardware and platform
resources, as well as sharing of those resources and the components that they support to serve several
large applications at the same time.

A fat client embeds business logic in the application at the client level.

CLIENTS/SERVER—ADVANTAGES AND DISADVANTAGES

Advantages
1. Performance and reduced workload:
Processing is distributed among the client and server unlike the traditional PC database, the
speed of DBMS is not tied to the speed of the workstation as the bulk of the database processing
is done at the back-end.

2. Workstation independence:
Users are not limited to one type of system or platform. In an ORACLE-based Client/Server
system the workstations can be IBM – compatible PCs, Macintoshes, UNIX workstations, or any
combinations of the three.

3. System interoperability:
Client/Server computing not only allows one component to be changed, it also makes it is
possible for different type of components systems (client, network or server) to work together.

4. Scalability:
The modular nature of the Client/Server system may be replaced without adversely affecting the
rest of the system.

5. Data integrity: Client/Server system preserves the data integrity, DBMS can provide number of
services that protect data like, encrypted file storage, real time backup (while the database is
being accessed), disk mirroring (where the data is automatically written to duplicate database on
another partition of same hard disk drive), disk duplexing (where the data is automatically
written to a duplicate database on a different hard disk drive), transaction processing that keeps
the track changes made to the database and corrects problems in case the server crashes.

6. Data accessibility (enhanced data sharing): Since the server component holds most of data in a
centralized location, multiple users can access and work on the data simultaneously.
 7. System administration (centralized management):
Client/Server environment is very manageable. Since data is centralized, data management can
be centralized. Some of the system administration functions are security, data integrity and back
up recovery.

8. Integrated services:
In Client/Server model all information that the client is entitled to use is available at the desktop,
through desktop interface, there is no need to change into a terminal mode or to logon into
another processor to access information.

9. Sharing resources among diverse platforms:

Client/Server model provides opportunities to achieve open system computing. Applications can
be created and implemented without much conversance with hardware and software.

10. Masked physical data access:

SQL is used for data access from database stored anywhere in the network, from the local PC,
local server or WAN server, support with the developer and user using the same data request.

11. Location independence of data processing:

Users log into an application from the desktop with no concern for the location or technology of
the processors involved. In the current user centered word, the desktop provides the point of
access to the workgroup and enterprise services without regard to the platform of application
execution.

12. Reduced operating cost:

Computer hardware and software costs are on a continually downward spiral, which means that
computing value is ever increasing. Client/Server computing offers a way to cash in on this
bonanza by replacing expensive large systems with less expensive smaller ones networked
together.

13. Reduced hardware cost:

Hardware costs may be reduced, as it is only the server that requires storage and processing
power sufficient to store and manage the application.

14. Communication costs are reduced:

Applications carry out part of the operations on the client and send only request for database
access across the network, resulting in less data being sent across the network.

Disadvantages

1. Maintenance cost:
Major disadvantages of Client/Server computing is the increased cost of administrative and
support personnel to maintain the database server. In the case of a small network, the network
administrator can usually handle the duties of maintaining the database server, controlling the
user access to it, and supporting the front-end applications.
2. Training cost:
Training can also add to the start-up costs as the DBMS may run on an operating system that the
support personnel are unfamiliar with.

3. Hardware cost:
There is also an increase in hardware costs. While many of the Client/Server database run under
the common operating systems (Netware, OS/2 and Unix) and most of the vendors claim that
the DBMS can run on the same hardware side by side with the file server software.

4. Software cost:
The overall cost of the software is usually higher than that of traditional PC based multi-user
DBMS.

5. Complexity:
With so many different parts comprising the entire Client/Server, i.e., the more are the pieces,
which comprise the system the more things that can go wrong or fail. It is also harder to pinpoint
problems when the worst does occur and the system crashes. It can take longer to get
everything set up and working in the first place. This is compounded by the general lack of
experience and expertise of potential support personnel and programmers, due to the relative
newness of the technology.