This documentation is for WSO2 API Manager 1.8.0 View documentation for the latest release.
Page Comparison - Configuring Caching (v.9 vs v.10) - API Manager 1.8.0 - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Caching at API Gateway

When  caching is enabled at the Gateway and a request hits the Gateway, it first populates the cached entry for a given token. If a cache entry does not exist in cache, it calls the key manager server. This process is carried out using Web service calls. Once the key manager server returns the validation information, it gets stored in the Gateway. Because the API Gateway issues a Web service call to the key manager server only if it does not have a cache entry, this method reduces the number of Web service calls to the key manager server. Therefore, it is faster than the alternative method.


An API's resources are HTTP methods that handle particular types of requests such as GET, POST etc. They are similar to methods of a particular class. Each resource has parameters such as its throttling level, Auth type etc.

When a user makes a request Users can make requests to an API through any of its defined resources, the resource-level parameters are cached in by calling any one of the HTTP methods of the API's resources. The API Manager uses the resource cache , at the Gateway node . For example, if you make a GET request to the API, its to store the API's resource-level parameters (Auth type and throttling level is cached). This The cache entry is identified by a cache key, which is based on the API's context, version, request path and HTTP method. Caching avoids the need to do a separate back-end call to check the Auth type and throttling level of a resource, every time a request to the API happenscomes. It improves performance.