Internet is essentially a design — a design of networks that allows communication between computers reliably and in a fault-tolerant way.
The internet is the foundation upon which websites, apps, and digital products exist. Without understanding its basics, you cannot fully grasp how your product reaches users or how data flows behind the scenes. The actual job is to see the internet not as a monolithic entity, but as a network of networks — a design that connects computers worldwide.
This lesson unpacks that design and the key protocols that enable reliable data transfer. You will learn how data travels in packets, how IP addresses uniquely identify devices, and how protocols like TCP/IP and DNS orchestrate communication invisibly but indispensably.
The internet is a network of networks, not just a network of computers
At its core, the internet connects millions — now billions — of computers across the world. But it is not just a simple network. It is a network of networks. Each network could be a home Wi-Fi network, a corporate intranet, or a telecom backbone.
Think of the internet as the system of roads, highways, flyways, and shipping lanes that connect cities and countries. Just as roads physically connect homes and businesses enabling people and goods to move, the internet connects computers and devices, enabling information to move.
The design of the internet is fault-tolerant. If one route is unavailable, data finds a different path. It scales seamlessly from a handful of connected devices to billions.
Technology for Managers Masterclass, Pragmatic Leaders
Talvinder Singh: “The internet works well whether it connects four computers or four billion. The key is the design — a network of networks that can route information reliably even if parts fail.”
Student: “So it's like multiple roads and highways that can reroute traffic if one is blocked?”
Talvinder Singh: “Exactly. This design principle is what makes the internet resilient and scalable.”
Understanding the internet as a design, not just infrastructure, is critical for product managers collaborating with tech teams.
Why protocols matter: TCP/IP as the common language
Every computer on the internet is different — different hardware, software, and operating systems. For them to communicate, they need a common language or protocol.
TCP/IP (Transmission Control Protocol/Internet Protocol) is that language. It defines how data is broken into packets, addressed, transmitted, routed, and reassembled at the destination.
Imagine the postal system: no matter what you send, it must fit in envelopes of standard size. Similarly, data is broken into packets — small chunks of information with headers that include metadata like source and destination IP addresses, sequence number, and timestamp.
TCP ensures that packets arrive reliably and in order. If packets are lost or arrive out of sequence, TCP requests retransmission or reorders them.
IP addresses: The unique identifiers of computers
Every device connected to the internet has a unique identifier called an IP address. This functions like a postal address or a PAN card number — it tells the network where the data should go.
IP addresses typically have the format nnn.nnn.nnn.nnn, where each nnn is a number from 0 to 255. For example:
- facebook.com resolves to 69.63.178.11
- A local device might have 192.168.1.10
When you send data, the packet includes both the source IP (who sent it) and the destination IP (who should receive it). This allows routers and servers to direct packets properly.
Product team discussion about network basics
Talvinder Singh: “Think of IP addresses as the 'to' and 'from' addresses on a letter. Without them, the internet wouldn’t know where to send data.”
Priya (PM): “So DNS translates domain names like facebook.com into IP addresses?”
Talvinder Singh: “Exactly. DNS is like the phonebook of the internet.”
Understanding IP and DNS is key to grasping how web requests resolve.
How DNS translates domain names into IP addresses
Humans remember names better than numbers. That's why we use domain names like google.com instead of IP addresses.
The Domain Name System (DNS) acts like a distributed directory. When you type a website into your browser, your computer asks DNS servers to translate that domain into the corresponding IP address.
The process works like this:
- You enter the domain name in your browser.
- Your browser queries the Name Server (NS) to find where the DNS records for that domain reside.
- The NS responds with the IP address of the DNS server holding the records.
- Your browser queries that DNS server for the IP of the website.
- The DNS server replies with the website’s IP address.
- Your browser connects to that IP to load the website.
This multi-step resolution happens in milliseconds but is critical for internet navigation.
- Pick a website you use frequently, such as flipkart.com or swiggy.com.
- Use the
nslookupordigcommand in your terminal to find its IP address. - Note the NS servers involved in the lookup.
- Reflect on how your browser finds the IP behind the scenes.
- Discuss why DNS is necessary instead of typing IP addresses directly.
Data packets find their way through a complex network
When you send data over the internet — say, a message or a video request — it travels in packets. Each packet can take a different route to the destination.
Routers and switches along the way decide the best path based on current network conditions. This is similar to how a courier might choose different roads or flights to deliver parcels faster or avoid traffic.
Because each packet carries metadata (source, destination, sequence), the receiving computer can reassemble the data correctly even if packets arrive out of order or via different paths.
This design makes the internet fault tolerant. If a route goes down, packets reroute automatically without losing data.
Tech team explaining data routing to PMs
Talvinder Singh: “Imagine sending a letter that breaks into multiple postcards, each taking a different route to the recipient.”
Neha (PM): “And the recipient knows how to put the postcards back together?”
Talvinder Singh: “Exactly. TCP/IP protocols manage that reassembly and ensure reliability.”
Understanding fault tolerance and routing helps PMs appreciate performance and reliability challenges.
The internet’s simplicity enables innovation
The internet is designed to be simple and generic. It carries all kinds of digital data — text, images, video, voice — without caring about the content.
This simplicity means anyone can run new applications over the internet without asking permission or changing the network. That is why innovations like WhatsApp, Instagram, and Razorpay could flourish on the same infrastructure.
Because the internet carries packets of data agnostically, new protocols and applications can be layered on top without disruption.
The layers of the internet: from physical cables to applications
The internet is built in layers:
- Physical layer: Cables, fiber optics, satellites, cell towers carry raw bits.
- Data link layer: Handles communication between devices on the same network.
- Network layer: Routes data between different networks using IP addresses.
- Transport layer: TCP manages reliable transmission and packet ordering.
- Application layer: Protocols like HTTP, FTP, SMTP enable web browsing, file transfer, email.
As a PM, you don’t need to become a network engineer, but understanding these layers helps you communicate with technical teams and appreciate trade-offs in performance and reliability.
Product design review
Talvinder Singh: “When your app feels slow, it could be a problem at any layer — the physical connection, routing, or application design.”
Priya (PM): “So knowing these layers helps us diagnose issues better?”
Talvinder Singh: “Exactly. It also informs decisions about caching, CDNs, and offline modes.”
Layered understanding aids product decisions about performance and user experience.
Test yourself: Diagnosing slow app performance in Mumbai
You are PM at a fintech startup in Mumbai. Users report slow loading times in certain neighborhoods. The engineering team suspects network issues.
The call: How do you investigate whether the problem is due to the internet’s physical layer, routing, or application design?
Your reasoning:
You are PM at a fintech startup in Mumbai. Users report slow loading times in certain neighborhoods. The engineering team suspects network issues.
Your task: How do you investigate whether the problem is due to the internet’s physical layer, routing, or application design?
your reasoning:
From the field: Why every Indian PM should understand internet basics
Where to go next
- Understand how tech stacks work: How Tech Stacks Work
- Learn about APIs and their role: The World of APIs
- Explore product design for Indian network conditions: Designing for India’s Connectivity
- Develop your technical fluency: Technical Concepts for Product Managers
- Prepare for AI-powered products: AI Product Strategy