In Edge, you can define an environment-scoped cache in the UI, and you can explicitly create caches with the management API.
But if you *don't* explicitly create a cache, a default org-level cache still exists. This cache doesn't show up in the list of environment caches in the UI, and it's not visible to the management API.
It's apparently available to policies (and Node.js), though.
For example, on the cache policies, there's a CacheResource element that lets you identify the cache to populate/look up/invalidate. If you don't include this element in a policy, the policy supposedly works on the 'default, shared' cache. (In Node.js, you apparently reference the shared cache with the name 'undefined').
So the big question is, is there an explicit name for the 'default' or 'shared' cache (like 'undefined' in Node.js)? For example, if I wanted to clear that cache with the management API, what name would I use?
Answer by Madhan+Sadasivam
·
Mar 19, 2015 at 01:11 PM
The default cache cannot be managed using the management API. This is the primary motivation for creating a named cache.
Answer by naveen · Mar 20, 2015 at 12:54 AM
For the default system cache we don’t require a “name” for the cache resource.The <CacheResource> tag is “optional” field.
You can manage the default system cache via OOTB caching policies but not management API calls.
Thanks, Naveen. So by manage the default system cache via policies, do you mean that by not including the CacheResource element, the policy works on that cache automatically? So no specific name to be used?
What is the size and TTL for the shared (default) cache when it's not used? 1 Answer
How can I fetch expired cache if my API fails from apigee edge 1 Answer
if there is a way to skip caching in L2 1 Answer
Clear multiple cache entries using a single invalidate cache policy flow 0 Answers
Can't I store an object in the Cache? 2 Answers