Loading…
Loading…
Add the operations your service exposes. Method, path, and status codes make your API much easier to review.
Policies that aren't specific to a single endpoint — auth, rate limits, versioning, and other notes.
Diagram
Draw the components and how traffic flows between them. Notes below the canvas are optional — the Walkthrough panel is the primary place to narrate flows.
Request walkthrough
Trace each core requirement as an ordered sequence of hops through your diagram. Use component names from your canvas for the From / To columns.
Given a prefix string, return top 5-10 ranked suggestions.
Suggestions ranked by a combination of query popularity and recency.
Suggestions update as new popular queries emerge (within minutes, not real-time).
Storage schema
For each entity, declare how it's stored. Sharding key is the interesting one — pick the access pattern it optimises for.
A search string with associated popularity score and metadata.
A character sequence typed so far. Maps to a set of candidate queries.
A ranked query returned to the user, with score and display metadata.
Component choices
Pick one per row and give a one-line reason. These are the concrete technology decisions your diagram implies.
How traffic is distributed to your app servers.
Where hot reads are served from.
Primary durable store for entities.
Your diagram
No components drawn yet — edit the diagram before answering.
Iterate on your design — don't start over.
Each scenario below probes a specific weakness in a typical HLD. Reference components from your diagram by name, describe what breaks and at what load, then name the minimum change that fixes it. Strong answers identify the precise failure mode — not just "scale it up".
A celebrity dies and millions search their name within minutes. Your trie was rebuilt 10 minutes ago. What do users see?
Probes: high level architecture