Skip to main content

Command Palette

Search for a command to run...

Understanding Network Devices

Published
4 min read
S
A front-end developer who’s always learning, building projects, and writing blogs to simplify web concepts

Introduction: How the Internet Reaches Our Home or Office

When we open a website deploy an API or make a database request a surprisingly large number of network devices work together behind the scenes to make that request succeed.

What Is a Modem and How Does It Connect to the Internet :-

A modem is the bridge between the local network and our Internet Service Provider (ISP).It Convert ISP signals (fiber, cable, DSL) into digital data that network can understand. Also Establish and maintain a connection with the ISP. Think of a modem as a translator. Our ISP speaks one language, home or office network speaks another. The modem translates between them. Without a modem our network is completely isolated from the internet.

What is a Router and how it directs traffic :-

A router decides where data should go. A router is responsible for Routing traffic between different networks local to internet. Assign local IP addresses usually via DHCP. Perform Network Address Translation. Routers allow multiple devices to share one public IP. It also isolate your internal network from the internet.

Modem connects us to the internet . And Router manages and directs traffic within and outside our network. Many home devices combine both, but logically they are still separate roles.

Switch vs Hub: How Local Networks Actually Work:-

A hub is a very basic networking device. It responsible for Broadcast incoming data to all connected devices A hub is like shouting in a room everyone hears the message even if it’s not for them.

A switch is the intelligent counterpart to a hub. While a hub indiscriminately broadcasts incoming data to all devices, a switch forwards data only to the intended device based on its MAC address. This targeted forwarding dramatically improves network efficiency and reduces congestion.

We can think of a switch like a postal worker who delivers letters directly to the correct house rather than shouting out the recipient’s name in a public square. By ensuring data reaches only its intended destination, switches minimize unnecessary network noise.

Switches matter because they enable faster communication, reduce network collisions, and enhance security. In practical terms, our networks rely on switches to ensure performance and stability. Hubs, by contrast, are inefficient, since they broadcast data to all connected devices, leading to performance bottlenecks and security vulnerabilities.

In modern networks, switches are the standard, as they enable organized and efficient traffic management. Our local networks would be chaotic without them.

What is a Firewall and why security lives here :-

A firewall is the guard of our network. It decides what is allowed to enter and what must stay out. Every request that comes from the internet must pass through the firewall first. If something looks unsafe it gets blocked right there.

We can think of a firewall as a security gate at the entrance of our building. Only people with permission are allowed inside. Everything else is stopped before it can cause trouble. This is why security lives here. Once bad traffic is blocked at the firewall our internal systems stay safe.

In real systems our APIs databases and servers sit behind a firewall. This means even if someone knows our server address they cannot directly access it without passing security checks.

What is a Load Balancer and why scalable systems need it :-

A load balancer helps when many users visit our application at the same time. Instead of sending all traffic to one server it spreads the traffic across multiple servers. This keeps the system fast and stable.

We can imagine a load balancer like a person managing lines at a busy counter. Instead of letting everyone stand in one long line people are guided to different counters. This way no single counter gets overloaded.

Scalable systems need load balancers because one server is never enough in real production. When traffic grows our system must grow too. Load balancers make this possible by sharing the load and keeping our application running even if one server fails.

How all these devices work together in a real world setup

When we open a website the request starts from our device and travels through many devices before reaching the server. First the request comes from the internet into our modem. Then the router decides where it should go. The firewall checks if it is safe. After that the load balancer sends it to one of the available servers. Inside the network switches help deliver data to the correct machine.

All these devices work together like a team. Each one has a single clear job. None of them replace the other. If even one is missing the system becomes slow unsafe or unreliable.

As developers understanding this flow helps us design better backend systems. Our code does not run in isolation. It runs inside this entire network setup. Knowing this makes us better engineers.