1

Module – 1 (Introduction)

Introduction to Client/Server computing - Driving forces behind Client/ Server, Client/

Server development tools, Development of client/server systems, Client/Server security,
Organizational Expectations, Improving performance of client/server applications, Single
system image, Downsizing and Rightsizing, Advantages of client server computing,
Applications of Client/Server.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 2

CLIENT SERVER ARCHITECTURE

Simply put, two factors are involved :

● A server is the one who provides requested services.

● Clients are the ones who request services.

Client-server architecture is a computing model in which the server hosts, delivers,

and manages most of the resources and services requested by the client. It is also

known as the networking computing model or client-server network as all requests

and services are delivered over a network. The client-server architecture or model

has other systems connected over a network where resources are shared among the

different computers.

Typically, client-server architecture is arranged in a way that clients are often

situated at workstations or on personal computers, while servers are located

elsewhere on the network, usually on more powerful machines. Such a model is

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 3

especially beneficial when the clients and server perform routine tasks. For

example, in hospital data processing, a client computer can be busy running an

application program for entering patient information, meanwhile, the server

computer can be running another program to fetch and manage the database in

which the information is permanently stored.

Client-Server architecture example

Here are some of the client-server model architecture examples from our daily life.

Hope it helps you to understand the concept better.

Mail servers

Email servers are used for sending and receiving emails. There are different

software that allows email handling.

File servers

File servers act as a centralized location for files. One of the daily life examples to

understand this is the files that we store in Google Docs. The cloud services for

Microsoft Office and Google Docs can be accessed from your devices; the files

that you save from your computer can be accessed from your phone. So, the

centrally stored files can be accessed by multiple users.

Web servers

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 4

Web servers are high-performance computers that host different websites. The

server site data is requested by the client through high-speed internet.

How does client-server architecture work?

To get a clearer picture of the process, let us learn how the browser interacts with
the server.

Please read the following steps for a better understanding of the process:

● The user enters the uniform resource locator (URL) of the website or file and
the browser sends a request to the domain name system (DNS) server.
● DNS server is responsible for searching and retrieving the IP address
associated with a web server and then initiating actions using that IP address.
● After the DNS server responds, the browser sends over an HTTP or HTTPS
request to the web server’s IP, which was provided by the DNS server.
● Following the request, the server proceeds to transmit the essential website
files required.
● Ultimately, the files are processed by the browser and the website is
subsequently presented for viewing.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 5

DRIVING FORCE BEHIND CSA

Client/server architecture is a computing model where the processing tasks are

divided between "client" devices (such as computers, smartphones, or tablets) and
a "server" that hosts resources or services. There are several driving forces behind
the adoption and popularity of client/server architecture:

● Scalability: Client/server architecture allows for scalable systems. As the

number of clients increases, additional servers can be added to distribute the
workload and handle increased demand. This scalability is essential for
applications and services with variable or growing user bases.
● Centralized Management: The server in a client/server architecture acts as a
central point for managing resources, data, and security. This centralization
simplifies maintenance and updates, making it easier to implement changes
across the system.
● Resource Sharing: In a client/server model, resources are centralized on the
server, and clients can access and share these resources. This includes
databases, files, and computing power, which promotes efficient resource
utilization.
● Data Integrity and Security: Centralized control over data and resources
allows for better management of security measures. Authentication,
authorization, and encryption can be implemented on the server to ensure
data integrity and protect sensitive information.
● Improved Performance: Client/server architectures often lead to improved
performance because tasks can be distributed between clients and servers
based on their capabilities. Heavy computational tasks can be offloaded to
powerful servers, while clients handle user interfaces and user interactions.
● Platform Independence: Clients and servers can run on different platforms
and operating systems. This flexibility allows clients to interact with servers
regardless of the specific technologies they use, promoting interoperability.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 6

● Networked Environment: The client/server model thrives in networked

environments, enabling clients to communicate with servers over local area
networks (LANs) or wide area networks (WANs). This facilitates remote
access to resources and services.
● Support for Thin Clients: Client/server architectures support the use of thin
clients, which are devices with minimal processing power and storage. Thin
clients rely on servers for most processing tasks, reducing the hardware
requirements for individual client devices.
● Modularity and Maintainability: By separating the client and server
components, it becomes easier to modify or upgrade one without affecting
the other. This modularity enhances maintainability and supports the
incremental development of applications.
● Cost Efficiency: Client/server architectures can lead to cost savings, as
resources can be shared among multiple clients. This reduces the need for
powerful individual client devices and allows for more efficient use of
computing resources.

In summary, the driving forces behind client/server architecture include scalability,

centralized management, resource sharing, data integrity, improved performance,
platform independence, networked environments, support for thin clients,
modularity, maintainability, and cost efficiency.

Development of CSA

The development of client/server systems involves creating applications that distribute

processing tasks between two distinct types of software entities: clients and servers.
This architecture is commonly used in networked environments to improve scalability,
manageability, and efficiency. Here's an overview of the key aspects involved in the
development of client/server systems:

​ Define System Requirements:

● Identify the functional and non-functional requirements of the system.
Understand the business goals, user needs, and performance
expectations.
​ System Architecture:

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 7

● Choose an appropriate client/server architecture based on your

requirements. Common architectures include two-tier (client and server),
three-tier (client, application server, and database server), and n-tier
architectures.
​ Choose Technologies:
● Select the programming languages, frameworks, and tools that best fit
your project requirements. Consider factors such as scalability,
performance, and compatibility.
​ Design the Database:
● Create a database schema that supports the data requirements of the
application. Define tables, relationships, and constraints. Choose a
database management system (DBMS) that aligns with your project goals.
​ Develop Server-Side Logic:
● Implement the server-side logic that handles business rules, processes
requests from clients, and interacts with the database. This may involve
using server-side scripting languages, frameworks, and middleware.
​ Implement Client-Side Interface:
● Develop the user interface on the client side. This includes designing and
implementing the graphical user interface (GUI) and any client-side logic.
Use appropriate technologies such as HTML, CSS, and JavaScript for
web-based applications.
​ Communication Protocols:
● Establish communication protocols between clients and servers. Common
protocols include HTTP/HTTPS for web applications, TCP/IP for general
networking, and other protocols specific to your application's needs.
​ Security Measures:
● Implement security measures to protect data during transmission and
storage. Use encryption, secure authentication mechanisms, and follow
best practices for securing both client and server components.
​ Testing:
● Conduct thorough testing to ensure the system functions as intended.
Perform unit testing, integration testing, and system testing. Pay attention
to performance testing and scalability testing to identify and address
potential bottlenecks.
​ Deployment:
● Deploy the client/server system in a production environment. Consider
scalability, reliability, and maintainability during deployment. Monitor the
system for any issues and address them promptly.
​ Maintenance and Updates:

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 8

● Regularly maintain and update the system to address bugs, add new
features, and improve overall performance. This may involve applying
patches, updating software components, and scaling the system to meet
growing demands.
​ Documentation:
● Document the system architecture, codebase, and any relevant
information for future reference. This documentation is crucial for
troubleshooting, maintenance, and knowledge transfer to other team
members.

Client/Server development tools

Here's a list of some popular tools commonly used for client/server development:

​ Integrated Development Environments (IDEs):

● Visual Studio: Developed by Microsoft, it supports various languages
including C#, Visual Basic .NET, and C++ for client/server development.
● Eclipse: Widely used for Java development, but also supports other
languages with plugins. It's open-source and supports client/server
development.
● IntelliJ IDEA: A popular IDE for Java development, which also supports
Kotlin, Scala, and Groovy. It has features tailored for client/server
applications.
​ Version Control Systems:
● Git: A distributed version control system widely used in the software
development industry.
● SVN (Apache Subversion): Another version control system often used for
managing source code and files in client/server projects.
​ Database Management Systems (DBMS):
● MySQL: An open-source relational database management system
(RDBMS) widely used in client/server applications.
● PostgreSQL: Another open-source RDBMS known for its advanced
features and reliability.
● Microsoft SQL Server: A relational database management system
developed by Microsoft, commonly used in Windows environments.
​ Frameworks and Libraries:
● [Link]: A runtime environment that allows you to run JavaScript on the
server-side, making it suitable for building client/server applications.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 9

● [Link]: A minimalist web application framework for [Link], often

used in building RESTful APIs for client/server communication.
● Spring Framework: Widely used for Java development, it provides
comprehensive infrastructure support for developing Java applications.
​ Networking Libraries:
● [Link]: A JavaScript library for real-time web applications. It enables
real-time bidirectional event-based communication.
● Netty: A high-performance networking library for Java, often used for
building client/server applications with high throughput and low latency
requirements.
​ Testing Tools:
● JUnit: A popular unit testing framework for Java.
● Mocha/Chai: JavaScript testing frameworks for [Link] applications.
● Selenium: A framework for automating web browsers, useful for testing
client/server web applications.
​ Containerization and Deployment:
● Docker: A platform for developing, shipping, and running applications
inside containers, useful for packaging client/server applications and
their dependencies.
● Kubernetes: An open-source container orchestration platform for
automating deployment, scaling, and management of containerized
applications.
​ API Development Tools:
● Swagger/OpenAPI: Tools for designing, documenting, and testing
RESTful APIs, ensuring compatibility and consistency in client/server
communication.

Organizational Expectations:
​ Policy Development:
● Establish and communicate security policies that outline organizational
expectations regarding client/server security. These policies should cover
data handling, access controls, and acceptable use.
​ Employee Training:

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 10

● Provide regular training sessions for employees to raise awareness of

security threats, best practices, and organizational policies. Educated
employees are a crucial line of defense against security breaches.
​ Incident Response Plan:
● Develop and regularly update an incident response plan to ensure a swift
and effective response to security incidents. This plan should include
communication protocols, escalation procedures, and steps for recovery.
​ Regular Audits and Assessments:
● Conduct regular security audits and assessments to identify vulnerabilities
and assess the effectiveness of security controls. Use external
penetration testing and internal audits to ensure a comprehensive
evaluation.
​ Compliance Management:
● Stay informed about industry regulations and compliance requirements
relevant to your organization. Ensure that your client/server systems align
with these standards to avoid legal and regulatory issues.
​ Security Awareness Programs:
● Implement ongoing security awareness programs to keep employees
informed about emerging threats and best practices. Encourage a
security-conscious culture within the organization.

Improving Performance of Client/Server Applications:

​ Database Optimization:
● Optimize database queries, indexes, and data structures to improve overall
database performance. Regularly analyze and fine-tune the database
schema for efficiency.
​ Caching Mechanisms:
● Implement caching mechanisms to store frequently accessed data,
reducing the need to fetch it from the server repeatedly. This can
significantly improve response times.
​ Load Balancing:
● Distribute incoming client requests across multiple servers using load
balancing techniques. This helps prevent server overload and ensures
optimal resource utilization.
​ Code Optimization:

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 11

● Optimize server-side and client-side code to reduce execution times and

improve overall responsiveness. Identify and eliminate unnecessary loops,
redundant code, and bottlenecks.
​ Content Delivery Networks (CDN):
● Use CDNs to distribute static assets such as images, stylesheets, and
scripts across geographically distributed servers. This reduces latency
and improves the loading speed of web applications.
​ Compression Techniques:
● Implement compression techniques for data transmission between the
client and server. This reduces the amount of data transferred, leading to
faster response times.
​ Asynchronous Processing:
● Employ asynchronous processing for tasks that don't require immediate
attention. This allows the server to handle multiple requests concurrently,
improving overall system performance.
​ Connection Pooling:
● Use connection pooling to efficiently manage database connections,
reducing the overhead of opening and closing connections for each client
request.
​ Resource Monitoring and Tuning:
● Continuously monitor server resources such as CPU, memory, and disk
usage. Use this information to identify potential performance bottlenecks
and optimize resource allocation.
​ Scalability Planning:
● Design the client/server architecture with scalability in mind. Consider
horizontal and vertical scaling options to accommodate increased user
loads. Plan for future growth to ensure sustained performance.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 12

Single System Image Mean?

A single system image (SSI) is a distributed computing method in which the

system hides the distributed nature of the available resources from the users. The
computer cluster, therefore, appears to be a single computer to users. This property
can be enabled through software mechanisms or extended hardware.

An SSI presents users with a globalized view of all the resources in the cluster,
irrespective of the nodes to which they are physically connected, while hiding the
fact that they are associated with different nodes. SSI also ensures multiprocessing
and an even load balancing among the systems. The machines focus on system
availability, scalable performance and transparency of resource management.

The features of a single system image include:

● Single User Interface: Users interact with the cluster through a single GUI.
● Single Process Space: Every user process holds a unique cluster-wide
process ID. A process on a node creates a child process on the same or a
completely different node. Communication between processes residing on
different nodes is also possible.
● Single Entry Point: Users connect to multiple nodes in the cluster through a
virtual host, which acts as single entry point. The connection request moves
to different hosts to balance the entire load.
● Single I/O Space: This permits all nodes to perform I/O operations on local
or remote disk devices.

The benefits of using a single system image include:

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 13

● It provides a similar syntax as that used in other systems, reducing operating

errors.
● Users can work in their preferred interface, which is then altered by the
administrator to manage the entire cluster as a single entity.
● It reduces cost of ownership and simplifies system management.
● It provides a straightforward view of all activities from a single node in the
entire cluster.
● The end user is not concerned about where the application runs.
● It avoids using numerous skilled administrators, because only one is needed
to centralize system management.
● It promotes standard tool development.
● It provides location-independent message communication.

Figure . A large single system image

DOWNSIZING AND RIGHT SIZING IN SSI

Downsizing and right-sizing in the context of Single System Image (SSI) involves
optimizing the resources allocated to the distributed system to match its actual

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 14

needs. Since SSI presents a unified view of multiple nodes or machines, managing
resources efficiently across the entire system is crucial. Here's how downsizing and
right-sizing apply to SSI:

Downsizing:

● Reducing Redundancy: In an SSI setup, there might be redundant resources

across nodes. Downsizing involves identifying and eliminating this
redundancy to free up resources.
● Consolidating Nodes: Downsizing may also involve consolidating nodes by
decommissioning or merging them, especially if certain nodes are
underutilized.
● Optimizing Workload Distribution: Downsizing includes redistributing
workloads across nodes to ensure balanced resource utilization and avoid
overprovisioning.
Right-Sizing:

● Matching Resources to Workload: Right-sizing ensures that each node

within the SSI has resources allocated proportionate to its workload. This
prevents both underutilization and overutilization of resources.
● Dynamic Resource Allocation: Right-sizing involves dynamically adjusting
resource allocations based on workload changes to maintain optimal
performance and efficiency.
● Cost Optimization: Right-sizing also considers cost implications, ensuring
that resources are allocated efficiently to minimize expenses while meeting
performance requirements.

Advantages:

● Cost Savings: Downsizing and right-sizing in SSI can lead to cost savings by
optimizing resource usage and avoiding unnecessary expenditure on
overprovisioned resources.
● Improved Performance: By ensuring that resources are appropriately
allocated, right-sizing can improve system performance by preventing
resource bottlenecks and ensuring smooth operation.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 15

● Scalability: Downsizing redundant or underutilized resources can free up

capacity that can be better utilized as the system scales up or handles
increased workloads.
● Simplified Management: With a more streamlined and optimized resource
allocation, management of the SSI becomes easier and more efficient.
● Implementation:
●
● Monitoring and Analysis: Implementing downsizing and right-sizing in SSI
requires continuous monitoring of resource usage and performance metrics
across the distributed system.
● Automation: Automated tools and algorithms can help in dynamically
adjusting resource allocations based on predefined thresholds or policies.
● Capacity Planning: Effective downsizing and right-sizing also involve
careful capacity planning to anticipate future requirements and adjust
resource allocations accordingly.

Advantages of Client/Server Computing:

Client/server computing is a model where tasks are divided between client devices
(such as computers or mobile devices) and server machines that provide services or
resources.

Advantages include:

● Scalability: Client/server architecture allows for easy scaling by

adding more client devices or servers as needed.
● Centralized Management: Servers can be centrally managed,
leading to easier administration and maintenance.
● Improved Performance: Distribution of tasks between clients
and servers can improve overall system performance.
● Flexibility: Client/server architecture supports various types of
clients and servers, enabling diverse applications and services.
● Reliability: Redundancy and fault tolerance mechanisms can be
implemented in server infrastructure to enhance reliability.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 16

Applications of Client/Server:

Client/server architecture is widely used in various domains, including:

● Database Management Systems (DBMS): Clients access

databases hosted on server machines.
● Web Applications: Clients (web browsers) interact with web
servers to access and manipulate data.
● File Sharing: Client devices connect to file servers to access
shared files and resources.
● Email Systems: Clients (email clients) communicate with mail
servers to send and receive emails.
● Enterprise Resource Planning (ERP) Systems: Clients interact
with server-based ERP applications to manage business
processes.

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE

 17

MODULE 1 CSA Prepared by Divya Visakh, AP, CSE