System Design · advanced
Search Platform Design
End-to-end design of a search platform: ingestion, indexing, query, ranking.
Mental model
A search platform splits into an ingestion/indexing path (durable, batchy, write-optimized) and a query path (low-latency, cacheable, read-optimized). Segment files, an object-storage tier, and an eval harness tie them together.
How to study Search Platform Design
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, Elasticsearch — Near real-time search, Apache Lucene — release documentation to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Search Platform Design with Search Systems, BM25. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Search platform end-to-end 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.
Common mistakes
- Designing the query path before the indexing path
- No segment/compaction story for updates
- Forgetting evals as part of the architecture
Learn from primary sources
Practice and explain it back
Search platform end-to-end
Design a product search platform: ingestion → analyzer → inverted index → query parser → ranking → result page. Identify where you would add a learned ranker.
Expected evidence: Pipeline diagram + the index update strategy (full rebuild vs near-real-time).
Open the interactive drill →Review prompts
- Why split a search platform into an indexing path and a query path?
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