Sure! We're using event-sourcing. An event might lead to a write into SpiceDB (

access_granted

or

user_created

or similar), or it might lead to a delete (

access_revoked

,

user_deactivated

). Sometimes both (

user_role_updated

). That's done by a Kafka consumer. I have a backlog of a few hundred million events to go through before it has caught up and starts processing new events in near-real-time, and at the moment I'm having to make at least 1 API calls per event: if

WriteRelationships

supported deletes by filter, I could process these events by batch which probably would be much much faster