Caching rules per team
The problem
In a supergraph, several teams own the types. A central list of cache rules belongs to none of them, every change waits for whoever owns the list, and it drifts as the subgraphs change.
With GraphPilot
Your subgraphs already declare their entity keys with @key. GraphPilot reads them from the supergraph you deploy, so they become cache keys without a second list. Extra keys or cache hints written in a subgraph need @composeDirective so composition keeps them. A mutation purges what it returned, whichever subgraph resolved it.
Docs: Federation routers and gateways ↗Transcript
Your supergraph is built by several teams: catalog, reviews, inventory, each with its own subgraph.
A central list of cache rules sits apart from all of them. Every change waits for whoever owns that list, and it drifts from the code.
Your subgraphs already declare their entity keys with @key. GraphPilot reads them from the supergraph you deploy: no second list to keep.
Extra keys or cache hints in a subgraph travel with composition, through @composeDirective.
A mutation purges what it returned, whichever subgraph resolved it.
Caching stays with the team that owns the data.
Cleared for takeoff
Start on Glider (Free).
No credit card, no commitment.
Prefer to talk first? Book a call