Token based caching

Google Cloud Apigee
1

We are implementing a design where in we are planning to cache the response in apigee .If we get a request for “GET INFO”, we make a call and store the response in cache resource. The next call comes to update the INFO , we update the INFO and invalidate the cache populated as part of “GET INFO” call.

So in order to implement this wanted to know which is more preferable :

  1. use of response cache with a cache resource.

  2. use of a custom resource cache (using populate , lookup and invalidation cache policy).

Our focus is more on performance aspect.

2

looking at performance aspect - both the approaches are just the same -

looking at development aspect - approach 1, using response cache, will be easier to manage - [it combines both lookup and populate into one policy]

all these policies can operate on a single cache resource, so it should be fairly straightforward to accomplish your usecases