Search Indexing Service · View 04 of 21 · People and journeys
What the trough tells the architecture
- The failure is not ranking. It is a stale availability field, caught after the tap — which is why availability, price and open/closed are fast lane with a 2-second p95 budget.
- The filter phase dips because post-filtering breaks facet counts and pagination: the design answer is mandatory pre-retrieval filtering, which view 20 enforces at query time.
- Deletion has no tolerated staleness at all, because the stale answer is a thing the user cannot have under any filter.
Assumptions
- 15,000 queries/second steady, 45,000 at the dinner-hour peak; query p95 ≤ 120 ms, p99 ≤ 250 ms.
- A consumer who is told 'no' twice in one session stops trusting the filters for the rest of it. This is an assumption about behaviour, not a measurement.
