1183
CHAPTER
Client/Server
Concepts
IN THIS CHAPTER
Distinguishing between the
client and the server
Understanding multi-tiered
computer systems
Understanding how Access fits
into client/server architecture
H
istorically, the term client/server has been applied to two-tier com-
puter systems. The fundamental characteristic of a client/server sys-
tem is that tasks are partitioned between two different computers.
One computer (the server) is primarily involved in providing some kind of
service, while another computer (the client) is usually charged with support-
ing a user interface and interacting with the user.
There are many kinds of servers: file servers, application servers, Web serv-
ers, printer servers, mail servers, and (the subject of this chapter) database
servers. The term server applies to both hardware and software. In a hard-
ware context, a server is (usually!) an exceptionally well-equipped computer,
with a lot of memory (often in excess of 16GB), large hard disks (several
terabytes is not uncommon in database servers), and an operating system
that is specifically designed for managing many, many resource requests at
one time.
Server computers are often arranged as clusters or farms, where multiple
computers, using their specialized operating systems, work together as a sin-
gle, really big computer. When working with a server cluster, a user isn’t
aware that more than a single computer is at work.
Server operating systems and software offer features and capabilities not
found in desktop operating systems. Generally speaking, server software is
specifically designed for multiuser operation, and provides greater security,
memory access, and optimization techniques not usually found in desktop
software.
Server software typically involves applications that are meant to be shared
among multiple users. An application like SharePoint is a good example. A
properly designed and maintained SharePoint installation can service hun-
dreds of simultaneous users with only minor performance issues.