Mutations clear what they change
The problem
With lifetimes alone, a cached answer stays stale until it expires. The usual way out is to flush everything on every write, and the origin pays for it.
With GraphPilot
A mutation sent through GraphPilot purges the cached responses that contained the objects it returned, by their keys, at every edge location, with no purge call. Everything else stays cached. Data changed outside GraphPilot is purged by key through the header, the API or the CLI.
Docs: Automatic invalidation ↗Transcript
A cache without keys handles a write in one of two ways. Wait for the time-to-live, and serve the old price until it runs out.
Or flush everything on every write, and send the whole shop back to your origin.
With GraphPilot, a mutation clears what it changed. setPrice returns book 42, and with it, its keys.
Every cached answer that showed book 42 is purged, at every edge location. Answers without it stay cached.
You write no purge call, and configure nothing: the keys come from your schema.
It works when the changed object is in the mutation's response. Data changed outside GraphPilot is purged by key, with a header, the API or the CLI.
Cleared for takeoff
Start on Glider (Free).
No credit card, no commitment.
Prefer to talk first? Book a call