Warm-keys read path
Last updated 2026-06-14
Definition
The warm-keys read path routes your common queries through a set of cache keys that Quri keeps populated. When you ask for a metric people read often, the answer comes from a warm key instead of being recomputed each time. You get a fast response, and Quri spends less work and cost rebuilding the same figure repeatedly.
How to do this in Quri
- Read your regular metrics in /app — common queries hit a warm key automatically.
- Notice that frequently viewed numbers return quickly because they are already cached.
- Quri keeps those keys populated so the next reader benefits too.
- Use refresh when you need a value recomputed rather than served from the warm key.
Frequently asked
- What makes a read “warm”?
- Quri keeps a populated cache key for queries that get read often. When your request matches one, the answer is served from that warm key instead of being recomputed, which is why common metrics come back fast.
- What if I ask for something uncommon?
- Then there is no warm key yet, so Quri computes it and may cache it for next time. The warm-keys path speeds up the queries people repeat; one-off reads still work, they are not pre-built ahead of time.