Hi Team! We were trying to integrate SpiceDB in one of our applications with backing data-source being PostgreSQL We are currently planning on deploying the same in kubernetes using the docker image (not the operator due to internal restrictions). As part of setting up the same - we came across the Watch API. I wanted to understand what is the use-case of this API the impact of not enabling the same in our instance?

Watch API is a change stream that clients can use to react to changes in SpiceDB. Think of it as a event system on relationship change. The API is enabled by default, unless you haven't set the proper configuration

track_commit_timestamp=on

required in PostgreSQL, in which case it automatically is disabled. I would assume that PG flag has a cost associated, but I don't know exactly what it is.

Okay interesting. I don't think we'll be watching the changes any-place in our application. Does this have any impact internally - as in assume that we have deployed multiple K-Pods of SpiceDB. Does Watch API have any impact on these internals (i.e. keeping state in-sync across multiple instances of SpiceDB)?

no, it's all stateful if calls to Watch API happen, otherwise no state is kept for that specific API

> not the operator due to internal restrictions) can you elaborate on your internal restrictions?