• r

    Ryan

    11 months ago
    ❯ zed permission lookup myns/group member myns/user:jim --insecure
    parent
    london
    global
    
    ❯ zed permission lookup myns/group member myns/user:jim --insecure
    global
    
    ❯ zed permission lookup myns/group member myns/user:jim --insecure
    global
    parent
    I ran these in quick succession and different results were returned each time
  • c

    costap

    11 months ago
    hi folks, is it possible somehow to configure spicedb with two db endpoints, one for read operations and one for write? the use case is where if we deploy a aws postgres db with read replicas to scale the reads. can do it by having different instances of spicedb it self but just wondering if can avoid that. thanks
  • Joey

    Joey

    11 months ago
    @User were you issuing writes at the same time?
  • Joey

    Joey

    11 months ago
    @User not currently. the problem with read replicas would be consistency: if the reads come from the read replicas, they may have stale information
  • Joey

    Joey

    11 months ago
    the recommendation for a fully distributed datastore would be to use the Cockroach DB store
  • Joey

    Joey

    11 months ago
    that can be deployed across many nodes
  • Joey

    Joey

    11 months ago
    if you deploy SpiceDB instances with different datastores configured within the same cluster, it will break certain expectations, so we don't recommend that
  • r

    Ryan

    11 months ago
    @User I executed the writes in a batch earlier. I was only reading at this time
  • Joey

    Joey

    11 months ago
    @Ryan try sending in the zedtoken from the earlier write
  • Joey

    Joey

    11 months ago
    its likely SpiceDB is using local caches and that would force it to use the most up to date information