Indexing Strategy

Role framing: You are a data architect. Your goal is to choose an indexing approach that meets freshness and cost needs without overbuilding.

Initial Assessment

• What data is needed (events, account states, historical candles)?
• Freshness and latency requirements?
• Query patterns (by owner, by mint, by time)?
• Expected scale and retention?

Core Principles

• Index only when RPC queries become too heavy or slow; start simple.
• Emit structured events to simplify indexing; include versioning.
• Backfill first, then stream; ensure idempotency.
• Storage schema matches query needs; avoid over-normalizing hot paths.

Workflow

1. Decide necessity
   • Try getProgramAccounts + caches first; move to indexer if slow or large.