You open your browser, you type google.com, less than a second later Google's page appears. So what exactly is happening between you pressing Enter and the page appearing? Your browser sees google.com, lakini remember computers use IP addresses; they do not know what google.com means. So the browser first asks, "What's the IP address for google.com?" To find the answer, it uses DNS, Domain Name System, which translates google.com to Google's IP address. Now, here's translation: from google.com to Google's IP address, that's called DNS resolution. So now we have the IP address, and the browser now knows where it's supposed to go. The request leaves your device, goes through a router, through your ISP, and multiple routers across the internet. Each router will be checking the destination IP and then forwards the request to the next best route toward Google. To establish a connection, we use communication protocols like TCP, so that's what your browser uses. Then TLS comes in and verifies that it's actually Google. Then it encrypts the whole connection, so it's protecting things like passwords, searches, cookies, etc. So now your browser sends its first HTTP request asking for Google's homepage. So this request passes through a firewall and a load balancer.
The firewall, to protect Google's systems, and the load balancer to distribute traffic to the best server. So after the best server has processed the request, it sends back the page's HTML. The browser receives the HTML, then it downloads all the other files that it needs, for example the CSS, the JavaScript, the images, and even the fonts. Finally, it combines everything together, and then it lays out the page, and you have Google's homepage. And all of that under a second.
Top comments (0)