CockroachDB datastore assumes linearizability about spicedb HOT 2 CLOSED

Instead of transactions ensuring that all nodes in the system have clocks in excess of the commit timestamp of a transaction before acknowledging it to the client, CockroachDB ensures that all nodes in the system have clocks in excess of the commit timestamp of a transaction minus the max_offset (a weaker guarantee) before acknowledging it to the client. This is satisfied trivially because, to this point, transactions have always written at or below "present time", which is by definition no further than max_offset ahead of the slowest node in the cluster. CockroachDB then implements uncertainty intervals on subsequent transactions to make up for this weakened guarantee and ensure linearizability just like Spanner.

from here

from spicedb.

More useful background material: https://forum.cockroachlabs.com/t/rare-race-condition-issue-with-as-of-system-time-across-selects/2610/10

from spicedb.