Search & IR · core
Search Systems
Inverted index, ranking, autocomplete at scale.
Mental model
A search system is a pipeline, not a scoring function: analyze -> inverted index -> cheap candidate retrieval -> expensive reranking -> serve. The first stage decides what the good ranker is ever allowed to see, so recall lost there cannot be recovered later. Autocomplete is a separate prefix index with its own latency budget, not a query against the main index.
How to study Search Systems
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use System Design Primer, Stanford IR Book — A first take at building an inverted index, Stanford IR Book — Wildcard queries (permuterm / k-gram indexes) to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Search Systems with BM25, Hybrid Search. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Browse vs search metrics and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Browse vs search metrics
Discovery feed: which metric — CTR, dwell time, or nDCG@10? Pick one for homepage browse, one for keyword search, justify in one line each.
Expected evidence: Browse: dwell/engagement; search: nDCG/precision@k.
Open the interactive drill →Review prompts
- Why can recall lost in candidate generation never be recovered by a better ranker?
Build evidence
Search platform design doc
An architecture doc for a search platform: ingestion, indexing, query, ranking.
- Separate ingestion/indexing and query paths
- Storage and segment/compaction story
- Capacity estimate and failure-mode review
Prerequisites
Related concepts
Learning paths
None assigned yet.