PEER TO PEER MODEL
. This means that CPU power and applications are
not centralized, but instead, every host has a CPU, and every host can run programs that
connect to other computers. The most common types of distributed networks are client/
server and peer-to-peer. It is important to know the differences between these so you can
decide which technology is best for any given customer scenario
The older type of computing was known as centralized computing. This was the case
during the days of the mainframe, where there was one supercomputer and the rest of the
devices that connected to the supercomputer were known as terminals (or dumb terminals).
They were strictly a keyboard and display with no processing power. Today’s computing
is known as distributive computing and is used for both client/server and peer-to-peer
networks. This means that every device or workstation has its own processing power.
However, in a way, the idea of centralized computing has made a comeback of sorts.
Terminal services and remote sessions to computers are based on the centralized computing
model. Also, thin-client computing has been slowly gaining in market share for the past
decade or so. Thin-client computers do not have a hard drive. Instead, they store an operating system in RAM, which is loaded up every time the device is turned on. All other applications and data are stored centrally. So, in a way, this is sort of blending some centralized computing in with today’s distributive computing
CLIENT SERVER MODEL
The client/server model is an architecture that distributes applications between servers,
such as Windows Server 2016, and client computers, such as Windows 8/8.1 or
Windows 10. It also distributes the necessary processing power. It is extremely common
in today’s LANs, as with most applications that an average user would utilize when
connecting to the Internet. For example, when users first come into work, they typically
log on to the network. Chances are this is a client/server network. They might be
using Windows 10 as the client computer to log on to a Microsoft domain, which is
controlled by a Windows server. A simpler example would be a user at home connecting
to the Internet. When a user wants to go to a website such as Bing, the user opens
a web browser and types http://www.bing.com/ (or one of many shortcuts). The web
browser is the client application. Bing’s web server is obviously the “server.” It serves the
web pages filled with highly functional HTML code. The client computer’s web browser
decodes the HTML code and fills the web browser display with data for both on-the-job
and personal use from the Internet from useful resources, such as Microsoft Outlook.
The outlook is the client application; it connects to a mail server, most likely an SMTP
server, perhaps run by Microsoft Exchange Server. The examples are endless, but client/
the server is not the end-all when it comes to networking. Sometimes, it is more efficient to
not use a server, particularly with a very small number of users
File Server A file server stores files for computers to share. The connection to a file server
could be made by browsing, by mapping a network drive, by connecting in the command
line, or by connecting with an FTP client. The latter would require special FTP server software to be installed and configured on the file server. By default, Windows Server 2008 and newer can be file servers right out of the box.
Print Server A print server controls printers that can be connected directly to the server
or (and more commonly) are connected to the network. The print server can control the
starting and stopping of documents, as well as concepts such as spooling, printer pooling,
ports, and much more. By default, Windows Server 2008 and newer can also be print servers right out of the box.
Database Server A database server houses a relational database, one that is made up of
one or more files. SQL databases fall into this category. They would require special software such as Microsoft SQL Server. Access databases (which are just one file) would not necessarily require a database server; they would usually be stored on a regular file server
Network Controller A network controller is a server, such as a Microsoft domain controller
that oversees user accounts, computer accounts, network time, and the general
well-being of the entire domain of computers and users. Windows Server 2016 servers can
be domain controllers, but they need to be promoted to that status. By default, a Windows
The server operating system is not a controller. Network controller operating systems are also
referred to as network operating systems (NOSs).
Messaging Server This server category is enormous. Providing simple services alone
would make this a full-time job, but you have to add in fax servers, instant messaging, collaborative,
and other types of messaging servers. For a Windows Server to control email,
special software known as Exchange Server needs to be loaded in addition to the operating
system.
Web Server Web servers are important to share data and give information about a company.
Windows servers can be web servers, but Internet Information Services (IIS) must be
installed and configured to do so.
CTI-based Server CTI is short for Computer Telephony Integration. This occurs when a
company’s telephone system meets the computer system. Special PBXs that are used to control
phones as a separate entity can now be controlled by servers with powerful software.