The documentation of resonsecache points to a CacheResource that you can define.
There is no option to set the cache under environments where it used to be in Edge.
How do we configure it in Apigee X? (documentation is lacking)
Solved! Go to Solution.
Yes, the documentation on the administrative API for cache resource entities is here.
It shows that you can list cacheresources and delete them.
But there is no operation to create a cache. In fact in Apigee X, the named caches get implicitly created at runtime when you reference one within a cache policy. This behavior eliminates the need to administratively create a cache resource, which is nice.
You asked: How do we configure it in Apigee X? In Apigee Edge, admins could specify cache properties, like maxElementsInMemory, and inMemorySizeKB. There is no possibility to do that in Apigee X.
The DELETE will clear the named cache. The next time a runtime policy refers to the named cache, it will get created anew.
helpful?
Yes, the documentation on the administrative API for cache resource entities is here.
It shows that you can list cacheresources and delete them.
But there is no operation to create a cache. In fact in Apigee X, the named caches get implicitly created at runtime when you reference one within a cache policy. This behavior eliminates the need to administratively create a cache resource, which is nice.
You asked: How do we configure it in Apigee X? In Apigee Edge, admins could specify cache properties, like maxElementsInMemory, and inMemorySizeKB. There is no possibility to do that in Apigee X.
The DELETE will clear the named cache. The next time a runtime policy refers to the named cache, it will get created anew.
helpful?
@dchiesa1 one question related to limits of number of cache. What happens if number of cache limit is breached? Will the cache be created? Will the API be succeeded or fail? I guess for items in cache, any new entry should be able to be accommodated by removing one. What is the criteria used for such removal?