Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Caching responses #13

Open
bboure opened this Issue Apr 4, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@bboure
Copy link

bboure commented Apr 4, 2019

It would be great to be able to cache responses from response mapping templates.
The way it could work is that AppSync caches the request-response pair. For any subsequent identical request, AppSync would serve the cached response.

It would be useful, for example, if you have a query executing a lambda which executes heavy calculations. The second time, the result could just be returned from cache. This would even save money since the lambda does not even have to run.
It should work with any data source type. There are many advantages. For example, with HTTP, you would save round trips with the remote server (and possibly avoid throttling), with DynamoDb, save throughput, etc.

Maybe a way to do it would be to have a new ElasticCache Data Source, which would call another Data Source to resolve the value initially or serve the cached value?

@jbailey2010

This comment has been minimized.

Copy link

jbailey2010 commented Apr 5, 2019

Hi,

Thanks for the feedback! This is a request we've heard before, and I'll note this as a +1 to prioritizing it for a future release.

Thanks,
Jeff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.