Ask questions[Feature request] Save/Cache API responses
As I am sure the developers have also noticed, APIs have quotas - and developing 99.99% requires you to retry/resend the same API requests (getting the same responses) which unnecessarily uses up your quota.
In a production sense, it is also feasible that poor quality or high quality disparate input datasets will produce reoccurring domains and making an API request for the same data in short intervals is wasteful.
With these 3 uses, the data caching is actually a very critical missing feature.
There are many viable options to chose from;
Hope this helps.
Answer questions chrisdlangton
@caffix this is wonderful news - thank you! I reviewed the diff and am not 100% sure but i don't think there was a way to specify where responses are save to (file system)?
It seems cache is pure graph database and responses are private to the app and users still cannot access their data from third party integrations..