Client-Server Report
Client-Server Report
lives, where whatever we need do virtually requires an internet connection. So, it is not only used
for computers but foe other technologies too. For instance, network architectures. There are two
types of architecture which is client/server architecture and peer-to-peer architecture.
Send request
Return result
Computer Server/Database
Although both architectures are popular, each of them has their pros’ and cons’ as well.
Client/Server architecture
Pros’ Con’s
1. Allows easier
1. Required skilled
sharing of data from
person to maintain
client to servers.
the server.
2. Reduces and avoids
2. Servers are literally
data duplication by
expensive
storing the resources
3. Security issues
in server rather than
in client.
3. Splits the process of
application across
multiple nodes [2]
Peer-to-Peer architecture
Pros’ Con’s
1. User performance
1. Increase in download
can be slowed due to
speed.
each node is
2. No need for a
accessed frequently
network operating
2. Resources cannot be
system
centrally backed up.
3. Easy architecture
3. Any intrusion or
setup
virus attacks is fully
4. No server is required
responsible by the
individual.
4. No securities besides
the permission
Diagram 1.4 shows a client/server architecture
simulated in packet tracer
A network tool called packet tracer is used as a simulation in order to create the client/server
architecture. 5 computers, 3 mobile phones, 1 router and 1 server are used in this representation.
Ip address is assigned manually for the wired devices and DHCP is used for the wireless devices
as the router is able to assign the IP address accordingly. For instance, if PC0 requests a data the
data is received by the router and sends it to the server. Then, the server returns back the packet
as per the PC0 request. If server fails, error message is sent back to the PC0.
IP address table
NODE IP ADRESS
PC0 192.168.0.3
PC1 192.168.0.4
PC2 192.168.0.5
PC3 192.168.0.106
PC4 192.168.0.107
SMARTPHONE0 192.168.0.101
SMARTPHONE1 192.168.0.103
SMARTPHONE2 192.168.0.105
SERVER0 192.168.0.2
ROUTER0 192.168.0.1
Diagram 1.4 shows a client/server architecture
simulated in packet tracer
NODE IP ADRESS
PC0 192.168.1.2
PC1 192.168.1.6
PC2 192.168.1.4
PC3 192.168.1.3
PC4 192.168.1.5
SMARTPHONE0 192.168.1.7
SMARTPHONE1 192.168.1.9
SMARTPHONE2 192.168.1.8
ROUTER0 192.168.1.1
Although web have been so popular these days, vulnerability and exploits do grow. In
order to reduce it, various securities are implemented to establish a secured connection between
network architectures. Firstly, client/server architecture uses :
Services provided via the internet are optimized when those services are located where
there are big pipes.
ISPs build their networks with a hierarchy of bandwidth, and even constrain some
customers’ (residential) bandwidth for uploading so they are less likely to be servers.
Content providers and other major web services can also be distributed in multiple
locations which are closer to the customers.
Because most users have a private IPv4 address and NAT is required for internet access,
each peer must access a central index server to get the location of a resource stored on
another peer.
o The index server helps to connect two peers, but after connected, the
communication may take place between the two peers without additional
communication to the index server – (TCP/UDP hole punching, NAT transversal).
[1]. Kratky, S., & Reichenberger, C. (2013). Client/Server Development based on the
Apple Event Object Model. Atlanta.
[5]. Sultan, N. (2010). Cloud computing for education: A new dawn?. International
Journal of Information Management, 30(2), 109- 116.