> Do you store all revisions in one huge LSM- tree indexed by the transactional start- and end-times Specifically, RocksDB uses an LSM tree whilst LMDB uses a

> Do you store all revisions in one huge LSM- tree indexed by the transactional start- and end-times Specifically, RocksDB uses an LSM tree whilst LMDB uses a B+ tree. You can get a feel for how Crux maintains its indexes here: https://github.com/juxt/crux/blob/master/src/crux/codec.clj#L25-L32 https://github.com/juxt/crux/blob/master/src/crux/codec.clj#... Crux doesn't natively track valid-to (end) times, but you can transact a Delete into the future to achieve the same logical result.