
Caching operates on distinct layers. When a computation starts, the service commits to a specific layer version so it does not mix old and new information mid-computation.
When building a resolve tree, the service:
The resolve tree is recomputed on a fixed schedule (default: every 10 minutes), controlled by:
federation.service.scheduling.resolver-reload-rate — reload interval (ISO-8601 duration, default PT10M)federation.service.scheduling.resolver-trigger-enabled — set to false to disable the scheduled triggerEach reload produces a new snapshot version, replacing the previous one.
A reload can also be triggered by a registry update notification sent to POST /registry/notify. The notification must be a signed JWT verifiable by the registry. This sets a refresh flag that is picked up on the next registry cron tick (every 1 minute), which then triggers a resolver reload if the registry state has changed.
When a request arrives, the service determines the newest snapshot version and uses that version’s local cache for the endpoint.
This ensures that cached responses from an older snapshot are never served in response to a newer snapshot’s requests.