ClientServer connection reuse helps, but unless it's something smarter than just reusing the TCP connection it's probably still going to hurt a little latency-wise; the N+1s I mentioned in the disclaimer usually involved connection reuse. Then again, I don't know if gRPC clients are doing something smarter. On SpiceDB's end, I'm not sure how that relates to N+1? Does SpiceDB wait some time for more requests coming down the pipe before firing off to the store? Or do you mean when the first one goes through, the second one hits an in-memory cache if the second request involves the same subject, or at least subject:resource combo? If so, which one is it? Thanks for the detailed answer btw.