Problem
Different application consuming the API’s but the backend has no idea who is consuming it and from where the request coming is from.
...
To avoid querying the datastore every time, we can cache custom entities in-memory on the node, so that frequent entity lookups don't trigger a datastore query every time, but happen in-memory, which is much faster and reliable than querying it from the datastore (especially under heavy load).
A. Lazy caching: Cache custom entities in-memory on the node on the first request, so that frequent entity lookups don’t trigger a datastore query every time (only the first time), but happen in-memory.
- Pros
- Size of cache will be less as it will cache the records that are in use.
- Cons
- Every first request will hit the datastore.
- For invalid app id request will hit the datastore every time.
...
B. Full table cache on kong service start: Cache the all the records exist in the table on every node immediately after kong service start, so entity lookups don’t trigger a datastore query every time.
- Pros
- No lookup on the data-store except initial so it will help for reducing latency in request response time.
- Cons
- If the database is size is large then the cache and invalidation process will take time.
- Every Node will query datastore after the start of service that will put a load on data-store for some time.
- It will cache the all records even if record not in use and that will unnecessarily increase cache size on every node.
Cache Invalidation
Every time a particular record is being updated, deleted in the datastore cache invalidation can be done, we can explicitly remove the cached record from the cache to avoid having an inconsistent state between the datastore and the cache itself. Removing it from the in-memory cache will trigger the system to query the datastore again, and re-cache that record. Caching will be done against consumer id so whenever particular consumer record updated only that record will be invalidated and re-cached.
...
$ curl -X DELETE http://localhost:8001/consumers/{consumer}/appids/{appid}
Retrieve the App ID
...
mapped to Consumer
...
$ curl -X GET http://localhost:8001/consumers/{consumer}/appids
...