Do you have a pointer to some doc explaining how to do that in foundationdb ?
https://blog.the-pans.com/notes-on-the-foundationdb-paper/ is one:
> Client (notice not Proxy) caches uncommitted writes to support read-uncommitted-writes in the same transaction. This type of read-repair is only feasible for a simple k/v data model. Anything slightly more complicated, e.g. a graph data model, would introduce a significant amount of complexity. Caching is done on the client, so read queries can bypass the entire transaction system. Reads can be served either locally from client cache or from storage nodes.
FoundationDB does this as well.