Structure Firebase Firestore data to avoid hot-spotting and cost blowups

domain: firebase.google.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Model for your queries: denormalize, one document read per screen where possible
  2. Avoid sequential document IDs (auto-IDs distribute writes)
  3. Paginate with query cursors (startAfter(docSnapshot)), not offset
  4. Aggregate with count()/sum() aggregation queries or maintained counters, not full-collection reads

Known gotchas

Related routes

Create a Firestore composite index to support multi-field queries with ordering
firebase.google.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans