Here's how we do it: https://wundergraph.com/docs/overview/features/caching https://wundergraph.com/docs/overview/features/caching We "persist" all operations u

Here's how we do it: https://wundergraph.com/docs/overview/features/caching https://wundergraph.com/docs/overview/features/caching We "persist" all operations using their name (unique) as part of the path. Variables are passed via query parameters. We also add a unique hash as query param which is generated by the configuration. This way, each "iteration" of the application invalidates the cache automatically. Additionally, we generate ETags for each request to reduce response payloads to zero when nothing changed. (https://wundergraph.com/docs/overview/features/automatic_content_revalidation_with_etags https://wundergraph.com/docs/overview/features/automatic_con...) Combined with the generated type-safe client, this is a very solid setup.