In present, we have two rocksdb instance for rooch and moveos. What we really want is that moveos could have its own rocksdb instance when embed into other application.
pros.
share buffer/cache, helping to improving performance and reducing hardware overhead
helping to add more batch operation
more atomic tx may improve consistence and integrity
TODO
share storage struct and method
simplify abstraction of storage (kvstore, codecstore, rawstore, rocksdbstore and _store are everywhere and mixed)
different options for column familys
hide rocksdb details (in present, StoreInstance is a pointer of rocksdb which makes hard to implement mock store)
In present, we have two rocksdb instance for rooch and moveos. What we really want is that moveos could have its own rocksdb instance when embed into other application.
pros.
TODO
related issues:
1593 #1588