What Happens When You Type https://www.google.com in Your Browser and Press Enter

Have you ever wonder how the internet work. Have you ever done something simple on the internet and wonder how it actually work. Well you are not the only one. In this blog post, we will take a deep dive into the journey of what occurs when you type “https://www.google.com" into your browser and hit Enter.
Join me as I unveil the web’s hidden gems:

• DNS request (The mystical)
• TCP/IP handshake (The powerful)
• Firewall (The guardian)
• HTTPS/SSL embrace (The secure)
• Load-balancers (The balancing act)
• Web servers (The skillful)
• Application servers (The ingenious)
• Databases (The treasure trove)

DNS request (The mystical)

DNS, or the Domain Name System, is like the internet's phone book. Instead of remembering the numerical IP addresses of websites, we use human-readable domain names, like "google.com". DNS is the system that translates these familiar names into the computer-friendly IP addresses that the internet uses to route data.
When you initiate that web search, your browser sets off on a quest to find the IP address associated with "google.com". It starts by sending a humble request to a DNS server. Think of the DNS server as a knowledgeable guide within the vast internet landscape.
The DNS server acts like a librarian who knows the location of every book (website) in the immense library (internet). It consults its index, seeking the IP address linked to "google.com". Once located, the DNS server generously shares this valuable information with your browser.

TCP/IP handshake (The powerful)

After your browser successfully collects google.com IP address from the DNS server, a pivotal moment in your internet journey unfolds - the TCP/IP( Transmission Control Protocol/Internet Protocol) handshake.
With the IP address in hand, your browser now knows where to direct its request. It sends out a subtle invitation in the form of a SYN (Synchronize) packet to the remote server. This packet carries a message: "I want to talk, and I'm initiating a conversation."
Upon receiving this invitation, the remote server responds with a SYN-ACK (Synchronize-Acknowledge) packet. This is the server saying, "I acknowledge your invitation, and I'm ready to engage in dialogue. Let's synchronize our communication.
To complete the handshake, your device sends back an ACK (Acknowledge) packet, confirming that it, too, is prepared to commence the conversation. This is the moment of agreement: "We are on the same page; let's start communicating."

Firewall (The guardian)

When you type "google.com" into your browser, the request your browser sends to Google's server goes through a firewall. This firewall checks the request to make sure it's safe and follows security rules.
As your data packets flow through the established connection, the firewall maintains its vigilant watch. It acts as a filter, scrutinizing the packets to ensure that only safe and authorized traffic is permitted to pass while blocking otential threats.

Packet Inspection in Action

Here's how the firewall's role unfolds after the handshake:

• Packet Inspection: Every data packet traveling back and forth between your device and the server is carefully examined by the firewall. It checks attributes such as source, destination, port, and protocol.
• Rule-Based Filtering: The firewall follows a set of predefined rules, often configured by network administrators. These rules dictate which types of traffic are allowed and which should be blocked. For instance, it might permit incoming web traffic (HTTP) but block suspicious traffic on unusual ports.
• Stateful Inspection: Advanced firewalls use stateful inspection to monitor the state of active connections. This allows the firewall to make context-aware decisions. For example, if you initiated an HTTPS connection, it ensures that only data relevant to that secure connection is allowed through.

HTTPS/SSL embrace (The secure)

HTTPS (Hypertext Transfer Protocol Secure) and SSL (Secure Sockets Layer) are twin guardians that work in tandem to create a secure pathway for data exchange between your device and google (web server).
Imagine your data as a treasure chest, and SSL as the lock that secures it. Here's how it works:

• Handshake: When you visit a secure website (identified by "https://" at the beginning of the URL), your device initiates an SSL handshake with the server. This handshake involves a cryptographic exchange of keys between your device and the server.
• Key Exchange: Once the handshake is complete, your device and the server both possess a shared secret key that's unique to this session. This key becomes the foundation of the encryption process.
• Data Encryption: As data flows between your device and the server, SSL encrypts it, converting it into a code that's incomprehensible to prying eyes. Even if intercepted, the data remains secure because the key to decode it is known only to your device and the server.
• Data Decryption: Upon reaching the destination (your device or the server), the encrypted data is decrypted using the shared secret key. This means that only the intended recipient can decipher the data.

Load-balancers (The balancing act)

Google.com isn't just a website; it's a gateway to a universe of information. With billions of users conducting searches, accessing services like Gmail and Google Drive, and viewing YouTube videos, Google.com must handle an enormous amount of traffic. This is where load balancers come into play.

The Role of a Load Balancer

• Even Distribution: Imagine millions of users knocking on Google's digital doors at any given moment. The load balancer's role is to evenly distribute these requests across a network of servers located in data centers worldwide. This ensures that no single server is overwhelmed, preventing slow responses or crashes.
• Traffic Monitoring: Load balancers continuously monitor the health and performance of servers. If a server in one data center is experiencing high traffic or issues, the load balancer can intelligently direct traffic to other data centers, ensuring uninterrupted service.
• Global Accessibility: Google.com is accessible from anywhere in the world. Load balancers help route user requests to the nearest or most suitable data center. This minimizes latency, ensuring that search results and services load quickly.
• High Availability: Load balancers enhance reliability. If one server fails, the load balancer can redirect traffic to healthy servers, minimizing downtime and ensuring uninterrupted service

Web servers (The skillful)

Once your request for "https://www.google.com" reaches Google's digital doorstep, it encounters the unsung hero known as the web server. This unassuming yet essential component plays a pivotal role in transforming your query into the familiar Google search page you know so well.
At its core, a web server is a specialized software or hardware system designed to receive, process, and respond to incoming requests from web browsers, like the one you're using. Think of it as the engine that powers the websites you visit.

The Journey from Request to Response

• Receiving the Request: Your request, containing the URL "https://www.google.com", arrives at one of Google's many web servers. These servers are distributed across multiple data centers worldwide for redundancy and speed.
• Processing the Request: The web server begins the process of interpreting your request. In Google's case, this typically involves processing search queries or handling other services like Gmail, Google Drive, or YouTube.
• Generating the Response: Based on your request, the web server retrieves the relevant information from Google's vast databases and services. For a search query, it consults Google's search index to find the most relevant results.
• Constructing the Web Page: The web server assembles the requested web page, incorporating HTML, CSS, JavaScript, and other resources. For Google.com, it builds the search results page with links and snippets.
• Sending the Response: Once the web page is constructed, the web server sends it back to your browser as an HTTP response. This response contains all the elements needed to render the Google search page on your screen.

Application servers (The ingenious)

Once your request for "https://www.google.com" is processed by Google's web servers and a web page is assembled, the journey continues as the request reaches the application server. This critical component is where the magic happens, transforming static web pages into dynamic, interactive experiences tailored to your specific needs.
An application server is a specialized software framework or environment that runs the software applications responsible for delivering dynamic content and functionality to users over the internet. Think of it as the brain behind the web server's brawn.

The Role of the Application Server

• Receiving the Request: The request from your browser, which now includes the HTML, CSS, and JavaScript code that makes up the Google search page, reaches the application server.
• Processing Dynamic Content: While the web server handles static content like HTML and images, the application server takes care of dynamic content and interactions. For Google.com, this includes processing your search query and generating personalized search results.
• Query Processing: When you enter a search query, the application server interprets it, consults Google's massive search index, and retrieves the most relevant search results for you.
• Personalization: The application server may also factor in personalization, taking into account your search history, location, and other parameters to tailor the search results to your preferences.
• Generating Responses: The application server generates dynamic content, such as the search results page, which includes the search results themselves, search suggestions, and other interactive elements.
• Collaboration with Databases: In some cases, the application server communicates with databases to fetch additional data required for your request. For instance, it might retrieve user account information when you log in or access saved settings.
• Interactivity: JavaScript code running on the application server enhances the user experience by enabling dynamic interactions, such as instant search suggestions, auto-complete, and real-time updates.

Databases (The treasure trove)

Once your search query travels through the intricate layers of web servers and application servers at Google.com, it eventually arrives at the heart of the operation (the databases). These digital repositories are where the vast wealth of information is stored, organized, and retrieved, powering everything from search results to personalized recommendations.

The Role of Databases

• Data Storage: Databases store the vast amount of information that makes up Google's index of the web, which includes web page content, metadata, and historical data. They also store user information like search history, account settings, and more.
• Data Retrieval: When you enter a search query or request specific information, the application server communicates with the databases to retrieve the relevant data. This process ensures that you receive accurate and up-to-date results.
• Indexing: Databases play a crucial role in indexing web pages, which involves analyzing and categorizing the content of billions of web pages to make them searchable.
• Personalization: Databases store user data and preferences, enabling personalized experiences. For example, they remember your search history to provide more relevant search results.

After traversing this intricate journey through DNS requests, TCP/IP, firewalls, HTTPS/SSL, load balancers, web servers, application servers, and databases, you finally receive the Google homepage. Your browser processes the HTML, renders the page, executes any scripts, and presents the final result on your screen.
In conclusion, typing "google.com" into your browser's address bar initiates a remarkable digital odyssey through a web of technologies and infrastructure. It involves layers of security, load balancing for efficiency, and the combined power of web servers, application servers, and databases. The next time you access your favorite website, appreciate the intricate processes that make it all possible.