Google Search System Design Explained Visually

Google Search

🔍

8.5 billion queries/day. Results in <200ms.

Crawl pipeline → Index pipeline → Query-serving pipeline

Guided Mode

Google Search: Three Pipelines

Request Flow

The scale

Google processes ~8.5 billion queries per day. Every query must return ranked, personalised results in under 200ms including network round-trips.

Three decoupled pipelines

Google Search is three pipelines running at completely different timescales: (1) the + + query-serving pipeline (<200ms); (2) the web crawl + build pipeline (hours/days); and (3) the + real-time suggestion pipeline (<20ms).

Why decoupled?

The crawl pipeline can be completely down for hours without affecting the query-serving pipeline. This decoupling is achieved via Kafka and hot-swappable index segments.

Key Insight

Google Search is not one system — it's three pipelines running at vastly different timescales, decoupled by design so each can fail, scale, and deploy independently.

Overview

Google Search

🔍

8.5 billion queries/day. Results in <200ms.

Crawl pipeline → Index pipeline → Query-serving pipeline

Guided Mode

Google Search: Three Pipelines

Request Flow

The scale

Google processes ~8.5 billion queries per day. Every query must return ranked, personalised results in under 200ms including network round-trips.

Three decoupled pipelines

Why decoupled?

The crawl pipeline can be completely down for hours without affecting the query-serving pipeline. This decoupling is achieved via Kafka and hot-swappable index segments.

Key Insight

Google Search is not one system — it's three pipelines running at vastly different timescales, decoupled by design so each can fail, scale, and deploy independently.

Overview