Design a Globally Versioned Key-Value Store

Versioned Key-Value Store With Global Versions The foundation of this design is a single monotonically increasing version counter shared by every key. Each write, regardless of which key it updates, consumes the next value from this counter. A key’s history is therefore sparse: it only contains entries for its own writes, while intervening global versions may belong to other keys. For example, suppose the store executes: The account history is: A historical read must answer…