ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to capture SpiceDB zedtokens from writes and use the at_least_as_fresh consistency level to guarantee that permission checks see the latest changes, avoiding stale reads after updates.
SpiceDB utilizes ZedTokens to maintain consistency across distributed datastores, ensuring that permission checks are performed against a snapshot at least as fresh as the provided timestamp. This mechanism is critical for preventing the "New Enemy" problem where revoked permissions might otherwise be granted due to stale cached reads. When a client requests
After a SpiceDB deployment, some CheckPermission calls appear to return outdated results even though the relationships were written successfully. The likely suspects are the consistency level used on the read path and how zedtokens are (or are not) being propagated by clients. My understanding is that each write returns a zedtoken, and reads can request mini
spicedb