👋 hi everyone, I’m curious whether anyone has experience with what is the most scalable of two approaches. For a definition, we have a relationship that determines whether a resource has been made sharable. If not set, it’s private. We now need to be able to display whether the resource is private in the UI. The two options we are considering are: caching the sharable state in the DB so when we load the resource we already have all the data we need to display it and we just need to do an access check on SpiceDB. This requires that we keep the DB and SpiceDB in sync. Or, we can add a second call to SpiceDB to check whether the relationship is there and augment the results we get from the DB. We’ll need this for both querying for a single resource as well as querying for a list of resources.

it'd help to know what this part of your schema looks like more concretely

@yetitwo It’s more like “has this thing been shared” Basically when we list these resources we want to show whether something remains private to you alone or not

right, but how is that expressed in your schema?

Kinda like this (excuse any syntax errors): definition user {} definition container { relation viewer: user permission view = viewer } definition thing { relation creator: user relation parent: container permission view = creator + parent->view }

do you already know the container in question?

Yeah

then issue a check:

thing:123#parent@container:abc

Well my question is not how to check SpiceDB. It’s whether checking SpiceDB to display this flag in the UI is best practice or whether caching it in the DB is best and keeping SpiceDB to access and permission checks.

mmm... in my head this is still an access question