You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2020. It is now read-only.
What feature are you missing?
I would like the graphql server spun up by graphcool deploy to have a caching layer that caches responses given the same query and variables.
How could this feature look like in detail? Tradeoffs?
For example, if my webserver or client makes a graphql query that selects a list of events filtered by country, the next time my webserver or client make the same query with the same country, it should serve the response from a caching layer rather than from disk. I should have the ability to specify the max age of the cache and the ability to invalidate it if necessary.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What feature are you missing?
I would like the graphql server spun up by graphcool deploy to have a caching layer that caches responses given the same query and variables.
How could this feature look like in detail? Tradeoffs?
For example, if my webserver or client makes a graphql query that selects a list of events filtered by country, the next time my webserver or client make the same query with the same country, it should serve the response from a caching layer rather than from disk. I should have the ability to specify the max age of the cache and the ability to invalidate it if necessary.
The text was updated successfully, but these errors were encountered: