When you don't want to use the included shared cache, you can create and configure your own cache. You can use the cache you create beneath caching policies, rather than using the shared cache.
You can also create a cache by using an Apigee API. For more, see Create a cache in an environment.
Cache limits: See Limits for the various limits that apply to caches, such as name and value size, total number of caches, the number of items in a cache, and expiration.
Defining a cache resource
You can create multiple cache resources in each environment. When you're configuring a caching policy, you specify whether the policy should use the included shared cache or a cache you created.
For data segregation, the scope of a cache is limited to the environment in which you created the cache. (For example, API proxies running in a 'test' environment cannot access data in a cache running in 'prod'.) Once you create a cache, policies can populate it with any serializable data. For usage, see Example: General purpose caching.
See also: Response Cache policy.
Creating and editing caches
These steps describe how to create or edit a cache using the management console.
- In the management UI, click the APIs menu, then click Environment Configuration.
- Select the environment for which you want to configure caches, such as test or prod.
- Go to the Caches tab.
- Click Edit.
- Under Caches, at the right side, click the +Cache button to add a new cache.
- Enter property values for the new cache. The following table describes the settings.
Property Name Default Value Description Notes Name N/A The name of the cache. Must be unique in the environment. Reference this cache from policies that interact with the cache resource. Description N/A An optional description of the cache resource. Expiration Type Timeout in Seconds Sets how cache entries will be expired. Entry time to live can be a specified number of seconds after creation, a specified time of day each day, or a specified date. Populate Cache policy and Response Cache policy both override these expiration settings with their own for cache entries they create. Expiration For timeout in seconds: 300 (seconds)
For time of day: 12:00:00
For date: current date (dd-MM-yyyy)
The configuration setting (either integer or dateTime) for the selection you made in the Expiration dropdown.
Enter time of day in the format HH:mm:ss, where HH represents the hour on a 24-hour clock. For example, 14:30:00 for 2:30 in the afternoon.
For the time of day, the default locale and time zone will vary depending on where the code is running (which isn't knowable at configuration time).
- Click Save.
You can populate cache during API proxy runtime in the following ways.