Hello Community
We are evaluating a possible option of caching some reusable backend data in API connect so that it can be used across multiple APIs. I know that the invoke policy has caching capabilities however out back side call is POST call and returns an ID token in response. I want to avoid writing an API proxy between the business API invoke and the backend service just to translate the operations to make use of the invoke policy caching.
I can see some custom policies in github that may be able to do it but we are also planning migrating from v5 to v10 in near future so I do not want to use the policy as it will not working in V10.
I would like to hear some advice on the way forward.
Regards
------------------------------
Vaibhav Mehra
------------------------------