How are concurrent writes managed using populate cache policy
Hi All,
How are concurrent writes managed using populate cache policy in multiple api proxies ?
The populate cache policy can use either the shared cache or the custom cache. If we are using the same cache object in multiple api proxies , how the cache will be populated during concurrent writes ?
If we are updating the same key value using multiple api proxies at same time, how will the cache behave ? Is the cache locked when it is updated by one api proxy ?
Any guidance will be helpful.
Thanks!
Hi @Neetu Garg - If the cache key name is exactly the same between proxies, the value will keep getting overwritten. To avoid that, take advantage of the many ways to uniquely and dynamically name keys, using the CacheKey and/or Scope elements, as described in the doc topic.
Hope that helps!
