---
title: "Design: a search service"
description: "Design a search service for team docs: two paths, keep enough to repair the index, follow one query, replace an index safely, and page through results."
canonical_url: "https://fanout.sh/system/archive/search-engine-system-design"
md_url: "https://fanout.sh/system/archive/search-engine-system-design.md"
last_updated: "2026-11-11"
access: "pro-preview"
---

# Design: a search service

Design a search service for team docs: two paths, keep enough to repair the index, follow one query, replace an index safely, and page through results.

- Access: Fanout Pro (public preview)

## The core idea

A search service turns a few words into an ordered list of documents.

For a team's documentation, that means finding useful matches while respecting edits, deletions and access changes.

## In this lesson

- Decide what the search box promises
- Two paths through the service
- Retain enough information to repair the index
- Follow one query
- An empty result has a boundary
- Replace an index without replacing the truth
- Add capacity where requests spend it
- Give later pages a stable position
- Run the update and deletion sequence
- Check usefulness as well as correctness

## Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.

---
This representation contains public Fanout content only. Protected Pro lessons, account data, billing, checkout, and pricing are not included.

Browse the public content map: https://fanout.sh/sitemap.md
