2. 10/03/2025 2
Subject Outline
• T1:Client/Server architecture & NOS Introduction
• T2: DNS and DHCP server management
• T3: Database and Web servers management
• T4: Storage Management
• T5:System backup and Archiving
• T6: Datacenter architecture
• T7: IT Monitoring
• T8: IT governance
• [Optional]: Server Virtualization
15. 10/03/2025 15
Computing Evolution
•Computing: designing and building hardware and
software systems for a wide range of purposes:
• processing, structuring, and managing various kinds of information;
• doing scientific studies using computers; making computer systems behave
intelligently;
• creating and using communications and entertainment media;
• finding and gathering information relevant to any particular purpose, and so on.
ACM Computing Curricula 2005
16. 10/03/2025 16
Computing Overview
• In the early days of computers, computer systems were
standalone systems
• there were no connections.
• had their own set of terminal and printer, and process data
independently.
• might used different operating system and software programs.
• Different and duplicated stored data forms.
• Inability to connect among each others.
17. 10/03/2025 17
Computing Overview
• standalone systems
How was the
world
without
networks/com
munications
?!
IS it valuable for
business
environment?
21. Centralized Processing
A host computer (often a mainframe) handles
all processing,
including input, output, data storage and retrieval.
Dump terminals can be used for data entry or
remote access
(NO PROCESSING).
22. Distributed Computing
• A collection of interconnected independent computers collaborate to
handle the processing.
•Independent?
• Each node (computer ) has its own resources (CPU, storage, memory,…).
• No shared memory.
• The end user fully utilizes his/her node, as well as, the resources of the remote
computer.
23. Distributed Computing
• world wide web (internet). Is the famous example.
• When you use a browser to visit a web site, a program such as Internet Explorer
runs on local system and interacts with a program(known as web server) which
runs on remote system to fetch a file or resource.
•I have full access on my
PC/Laptop (Independent)
•I can access any resource on
the internet (Interconnected)
25. Distributed Computing
• There are two models of distributed paradigm:
Asymmetric relation
Different Nodes with Different Roles
symmetric relation
Different Nodes with Same Roles
26. Peer-to-peer model
A class of decentralized, self-
organizing distributed systems, in
which all or most communication
is symmetric.” (IPTPS’02)
The load is divided among all the
involved components.
Each node is considered as both
server and client. (symmetric relation)
Each node contribute some
processing power and memory.
27. 10/03/2025 27
P2P model Application
Computation
• E.g. Seti@Home (Astronomy), UnitedDevices (Cancer Research), and
Gnome@home.
File Sharing
• Napster, FastTrack (KaZaA, iMesh), Gnutella (LimeWire, BearShare), Overnet,
BitTorrent, etc
Content Streaming
• Pplive, SplitStream, etc
• The first few users get the stream from the server
• New users get the stream from the server or from users who are already
receiving the stream.
29. 10/03/2025 29
Client Server Model
It is the most prevalent model for distributed computing protocols.
It is the basis of all distributed computing paradigms at a higher level
of abstraction.
It is service-oriented, and employs a request-response protocol.
30. Client-Server Model
•Each component of a
client-server system has
the role of either client or
server (Asymmetric
Relation)
• Client: a component that
makes requests
clients are active initiators
of transactions
• Server: a component that
satisfies requests
servers are passive and
react to client requests.
31. 10/03/2025 31
Client-Server Model
• Server
• manage network resources like Disk drives (file servers), Printers (print
servers), and Network traffic (network servers)
• Client
• Initiate the service (e.g. email client to send an email/ web browser to open
website)
• Rely on servers for: Files, Devices, Processing power.
• Fat client vs. Thin Client
35. 10/03/2025 35
Fat client vs. Thin Client
Fat clients (thin server)
The bulk of the application is running on the client
The client knows how the data is organized and where it is
Different clients access the same applications different ways
Fat servers (thin client)
The server more complicated
The clients are less complex
More of the code runs on the server
The network interaction is minimized
37. 10/03/2025 37
Server Types
File servers
File sharing and file processing
Data base servers
Passing file results
Example: Query in DBMS server
Typically one single request/reply
Transaction servers
Transaction server includes DBMS and transaction
monitoring
Server has remote procedures run online by the client
web servers
Super-fat servers and thin clients
Uses HTTP protocol
Java was first to introduce interactive C/S forms.
38. Two-Tier vs. Three-Tier Architecture
Two-tier servers
Examples: file servers and database server
The process (application logic) is buried within the client or server (or both)
Three-tier servers
Examples: Web and distributed objects
The process is run on the middle-tier – separated from the user and data
interface
They can integrate the data from multiple sources
More robust and more scalable
42. Middleware Software
a set of common business-unaware services that
enable applications (server) and end users (client)
to interact with each other across a network.
Allowing the client request for a service and the server providing it
Middleware can also be between server/server
Two broad classes
General
LAN servers, TCP/IP, Communication stacks, Queuing services, etc.
Application specific
Used to accomplish a specific task
Groupware specific: SMTP
Internet specific: HTTP
Database specific: SQL
43. 10/03/2025 43
Middleware Software
Web Browser
GUI
OS
Service-Specific; DSM
NOS (security, peer-to-peer,
directory, distributed files);
Transport stack (TCP/IP)
Web server
Groupware
DBMS
Etc.
Client
Middleware
Server
DSM: Distributed Shared Memory
46. 10/03/2025 46
Server Management
Server Management refers to the servers’ monitoring and
maintenance.
Maintenance ensures that every hardware and software run at its optimal
capabilities.
Monitoring involves keeping track of every metric and parameter that may
affect your server performing at full capacity.
How to do that?
This is the core of UCCN3004