Caching in Edge
Apigee Edge provides caching for runtime persistence of data across requests. You access the cache with policies, such as Populate Cache policy, LookupCache policy, InvalidateCache policy, and Response Cache policy.
Your organization includes access to a shared cache that is useful for most cases. You can also configure your own cache if you want finer control of performance.
You might want to use a cache to:
- Reduce latency and traffic. Requests are satisfied in a shorter time and with reused representations.
- Persist data across transactions. You can store session data for reuse across HTTP transactions.
- Support security. Scope access to cache entries so they can be accessed only in a particular environment or by a specific API proxy.
Get background and examples on the persistence features provided by Edge.
Find out how policies support general purpose caching, backend response caching, and key-value maps.
Understand the options for creating unique identifiers for cache entries.
Find out how the cache system is structured and how cache defaults interact with policies.
Learn how HTTP response headers are handled when you're using the ResponseCache policy.
Create your own caches when the included shared cache won't meet your needs.
Use these policies for persistence.
Put data into the general purpose cache.
Get data from the general purpose cache.
Remove a general purpose cache entry.
Get and put data from a backend resource.
Use a key/value map store for long-term persistence.
Use these APIs to work with caches.
Clears a cache entry using the cache key.
Creates a cache in an environment.
Gets information about a cache.
Clears cache entries. Can be scoped by cache key prefix.
Lists the caches in an environment.
Updates a cache in an environment.
Deletes a cache.
Help or comments?