Do Cached Reads in Tigris Count as Read Operations?

[lps]

I’m evaluating Tigris for my upcoming project and am impressed by its built-in global distribution and object caching features (as noted in the Tigris caching documentation).

In my previous projects, I typically used a CDN to cache read requests, which helped reduce costs by minimizing direct reads.

With Tigris, if I have a public object that is read once, will subsequent reads from the cache be charged as read requests within the same region? I’m trying to understand how the caching mechanism impacts billing for read operations.

Thanks for your insights!

[charsleysa]

@lps

will subsequent reads from the cache be charged as read requests within the same region?

My understanding is yes, every read is charged as a read regardless of where it was read from. The benefit comes from faster reads when using the cache and no egress fees.

[jmj]

Yes as @charsleysa mentioned, it will be charged towards read requests.