3 ms·
> which also had some ability to run your client as a cluster node that you alone get to query FoundationDB does this as well.
by svieira 4y ago
> which also had some ability to run your client as a cluster node that you alone get to query
FoundationDB does this as well.
- bsaul 3y agoDo you have a pointer to some doc explaining how to do that in foundationdb ?
- svieira 3y agohttps://blog.the-pans.com/notes-on-the-foundationdb-paper/ 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.