Added detailed explanation on DNS resolution and TLS handshake #2508
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my pull request, I have added a detailed breakdown of the DNS resolution process, TLS handshake, and load balancing mechanisms that occur when a user enters https://www.google.com in their browser and presses Enter.
Key Enhancements:
Expanded DNS Resolution Explanation:
Differentiated Recursive vs. Authoritative DNS queries.
Explained the caching mechanism at browser, OS, ISP, and root level.
Clarified how Google's Public DNS (8.8.8.8) optimizes lookups.
Added TLS Handshake Process:
Step-by-step breakdown of Client Hello, Server Hello, Key Exchange, and Finished handshake.
Explained how TLS encryption secures data in transit.
Mentioned TLS 1.3 improvements (e.g., 0-RTT handshake).
Load Balancing and Traffic Distribution:
Described how Google’s Global Load Balancer (GLB) distributes requests.
Explained how Google's Edge Network/CDN caches content for faster delivery.
Mentioned failover mechanisms and regional data centers.
Database Interaction & Page Generation:
Added details about how Google’s backend servers process requests.
Described how Google fetches index data from its distributed database.
Explained how search results are ranked and rendered dynamically.