Scribd
Upload
49 views4 pages

Network Architecture and Protocol

Networking

Uploaded by

Ginzil Haman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
49 views4 pages

Network Architecture and Protocol

Networking

Uploaded by

Ginzil Haman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Network Architecture and Protocol

Network architecture refers to a network’s structural and logical layout. It describes how the
network devices are connected and the rules that govern data transfer between them.

There are many ways to approach network architecture design, which depend on the purpose
and size of the network. Wide area networks (WAN), for example, refer to a group of
interconnected networks often spanning large distances. Its network architecture will be vastly
different from that of a local area network (LAN) of a smaller office branch
Planning the network architecture is vital because it either enhances or hinders the performance
of the entire system. Choosing the wrong transmission media or equipment for a particular
expected server load, for instance, can cause slowdowns on the network.
Most network architectures adopt the Open Systems Interconnection Model or OSI. This
conceptual model separates the network tasks into seven logical layers, from lowest to highest
abstraction.

The Physical layer, for instance, deals with the wire and cable connections of the network. The
highest layer, the Application layer, involves APIs that deal with application-specific functions
like chat and file sharing.

Types of Networking Architecture


These are the peer-to-peer and client/server architectures.
Peer-to-peer
In a peer-to-peer model, all devices in a network have equal responsibilities and privileges with
each other. This means tasks are allocated equally throughout the network. Files in one
computer can be shared with every other computer, essentially making every node a network
storage drive

A peer-to-peer architecture is suitable for small networks, such as a branch office. Your home
network, by the way, often uses a peer-to-peer model.

Client/server architecture

In a client/server architecture, all devices in the network, called “clients,” are connected
to a central hub, called a “server.” The server handles the bulk of the network
operations – data storage, processing of client requests, cybersecurity, and access
control.

Most large networks, such as WANs, often use the client/server model. The web server
you’re accessing this article on, for instance, is a perfect example. In this case, your
computer or smartphone is the client device. Client/server is also the preferred
enterprise network architecture.
Network Architecture Design

The design of any digital network architecture involves optimizing its building blocks.
These include:

Hardware

Transmission Media

Protocol

Topology

Network Protocol
A network protocol is a set of established rules that dictate how to format, transmit and receive
data so that computer network devices -- from servers and routers to endpoints -- can
communicate, regardless of the differences in their underlying infrastructures, designs or
standards.

To successfully send and receive information, devices on both sides of a communication


exchange must accept and follow protocol conventions. In networking, support for protocols can
be built into software, hardware or both.

Advantages and Disadvantages of Network Architecture

Different network architectures have their pros and cons; and knowing them is the key to picking
out the right one for your needs.

Peer-to-peer models are often inexpensive and easy to put up because you don’t need to invest in
a powerful server. Theoretically, all you need are network cables or a router, and you’re good to
go. It’s also quite robust; if one computer goes down, the network stays up. The distributed
nature also lessens or at least spreads out the network load to prevent congestions.

However, peer-to-peer models are harder to manage. Since there’s no centralized hub, you’d
need to configure each computer individually to set up, for example, security software. Thus,
peer-to-peer networks are also less secure. One hacked computer is all it takes to hijack the
network.
Client/server models, on the other hand, are easier to manage because they take on a centralized
approach. You can set up access privileges, firewalls, and proxy servers to boost the network’s
security. Thus, a client/server setup is best for large networks over larger distances.

The disadvantage of this approach is that a client/server architecture is more expensive to set up,
as you need a powerful server to handle the network load. It also requires a dedicated
administrator to manage the server, which adds to payroll.

But the biggest con of a client/server model is that the server is a weak link. If the server goes
down, the entire network shuts down. Thus, security is often the most robust at and near the
server.

You might also like