Hello SpiceDB team! I am evaluating SpiceDB for the use case, when WriteRelationships are rare and most traffic is CheckPermission. As I understand, for such a case it is safe to configure a reasonably high quantization window (so that revision cache ttl and dispatch cache ttl are long enough) while using ZedTokens to ensure new enemy problem is eliminated. Are my assumptions correct here?

Yes that's correct - this blog post has a lot of detail on quantization config, it may help you match to your use-case and pick a good number: https://authzed.com/blog/hotspot-caching-in-google-zanzibar-and-spicedb there are also metrics on cache hit rates that you can use to validate your configuration once you're up and running.

yeah, I've read that blogpost a couple of times already 🙂 at_least_as_fresh is a bit confusing for me since in my use case above (rare writes) with low revision cache ttl after some point-in-time it effectively becomes minimize_latency. hence I assume for higher performance I should configure SpiceDB such that revision ttl is like 1h, 2h, etc...

yeah, if writes are rare enough (regardless of what your quantization period is) then at_least_as_fresh will look like minimize_latency most of the time (which is good!)

got it, thanks!