Design Google Search: crawling, indexing, and ranking
Google Search
Guided ModeThe Cache-First Query Path
Request Flow
1
Browser to DNS to LB
User submits a query. The browser resolves DNS (1ms), receives a Google anycast IP, and connects to the nearest Load Balancer (2ms).
2
API Gateway checks the Result Cache
The API Gateway checks the Result Cache first. The top 1% of queries account for ~50% of all traffic. A cache HIT returns results in under 10ms total.
3
Cache miss path
A cache miss triggers the full query-serving pipeline. This is the minority path but must still complete in under 200ms.
Key Insight
The cache is the most important performance lever in the query path. Popular queries never touch the index — 200x faster than going to the inverted index.
Step 1 of 4
