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.
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.