Expand description
Implementation of Consensus backed by FoundationDB.
We’re storing the consensus data in a subspace. Each key maps to a subspace with the following structure:
./keys/<key> -> ()to track existing keys../data/<key>/<seqno> -> <data>mapping seqnos to data blobs.
The current seqno for a key is determined by a reverse scan of the data entries, rather than a separate head pointer. This ensures locality between the latest data and any metadata lookups.
Structs§
- FdbConsensus
- Implementation of Consensus over a Foundation database.
- FdbConsensus
Config - Configuration to connect to a FoundationDB backed implementation of Consensus.