Series
How does the internet actually reach your code? This 6-part beginner series covers network devices, DNS, DNS records, TCP, TCP vs UDP, and hands-on testing with cURL.
You open a website, and it loads in under a second. Looks like magic, right? Behind that one click, your request passes through a chain of devices: a modem, a router, a switch, a firewall, and maybe a
You type google.com and press Enter. Before a single byte of the page arrives, your computer has to answer one question: where is google.com? Computers don’t understand names. They understand IP addre
How does a browser know where a website lives? You type a name like mysite.com, and a moment later the page appears. But computers don’t understand names, they understand numbers. Somewhere in between
Imagine sending a 10-page letter by dropping each page into a different mailbox, with no page numbers and no way to know if any arrived. Some pages get lost. Some arrive in the wrong order. Some come
Imagine two computers on opposite sides of the world wanting to exchange data. Without agreed rules, it would be chaos. One side sends too fast, the other can’t keep up, and pieces get lost or jumbled
Every time you open a website or use an app, your device is talking to a server. A server is just a computer somewhere that stores data and answers questions. You ask, it replies. Usually your browser
