Question

A retail analytics team enabled the integrated cache via a dedicated gateway to reduce RU charges on a set of frequently repeated queries. Most queries now return RU charge of 0, but one high-volume query keeps showing full RU cost on every execution even though it is identical each time. Investigation shows the SDK client for that query sets the request consistency level to Strong, while the account default is Session. What is the most likely cause of the cache never being used for that query?

Accepted Answer

The integrated cache only serves requests made with Session or Eventual consistency; requests using Strong or Bounded Staleness bypass the cache entirely.

Answer

The MaxIntegratedCacheStaleness value must be explicitly set to zero for Strong consistency requests to be cached.

Answer

The integrated cache caches only point reads, so any query with a filter always incurs full RU cost regardless of consistency.

Answer

Strong consistency requires provisioned throughput above 100,000 RU/s before the integrated cache can be enabled.