Search Indexing Service  ·  View 03 of 21  ·  People and journeys

Actors and Their Core Journeys

Six parties, two of them machines, and what each is actually trying to get done.

Editable source SVG draw.io All views
People who search Consumer 40 M monthly Goal — Show me things I can actually have right now, not things that existed this morning. Core journeys Find something that exists 15 k queries/s Browse a filtered category People who publish Merchant 180 k active Goal — When I change my price, I want to see my own listing change — and believe it. Core journeys Publish a change p95 ≤ 2 s fast lane Check my own listing Catalogue Ops bulk editor Goal — Rename a brand across two million listings without breaking anyone's search. Core journeys Run a bulk parent edit People who own the index Search Engineer relevance owner Goal — Ship a ranking change I can prove helped, and undo it in a minute if it did not. Core journeys Ship a relevance change gate + variant split Add a judgement set Platform SRE on call Goal — Rebuild any index inside the RTO, and never be the person who hand-edits a live one. Core journeys Run a gated reindex Roll back by alias Machines in the cast Source Systems 4 integrated Goal — Emit my changes once and never be asked to serve a full table scan at 3am. Core journeys Emit a change stream Export a daily snapshot Reconciler 1 M docs/day Goal — Find the document nobody reported missing. Core journeys Sample and compare Actors and Their Core Journeys Person or role Journey / task External / third party Security / platform The reconciler is in the cast because the platform's worst failure has no complainant. v 1.0 · owner Data Platform Architecture

Decisions

  • The consumer's goal is stated as they would state it — things they can have now — which is why availability staleness is treated as a correctness problem rather than a freshness preference.
  • The merchant is a separate actor from catalogue ops because one checks their own change and the other changes two million documents; those are different requirements wearing one word, 'edit'.
  • The reconciler is in the cast because the platform's worst failure, a silently missing document, has no human complainant.

Assumptions

  • Search engineers own relevance and expect to ship weekly; SRE owns the index lifecycle and expects never to hand-edit a live index.
  • Source systems will accept emitting a change stream, but not a nightly full table scan of production.