Flat KV store is the most basic abstraction - a store that associates a single binary key with a single binary value.
By using a specific key separator these stores can implement hierarchical key-value store.
-
In-memory B-Tree
-
Pebble (experimental)
-
Downgrade of Hierarchical KV
-
Downgrade of Tuple store
| Backend | Persistence | Concurrency | Transactions |
|---|---|---|---|
| B-Tree | - | - | - |
| Badger | X | X | X |
| Pebble | X | X | - |
| LevelDB | X | X | X |
| Hie. KV | X | X | X |
| Tuple | X | X | - |
| Backend | Seek | Prefix |
|---|---|---|
| B-Tree | X | X |
| Badger | X | X |
| Pebble | X | X |
| LevelDB | X | X |
| Hie. KV | X | X |
| Tuple | X | X |
- Even though all backends expose
Txinterface, some may behave incorrectly during concurrent writes to the same key. This is why transactions support may be marked unavailable for some backends. Contributions welcome :) - Support for any of the features in meta-backends like tuple store will depend on when the underlying backend support.
- Some features may be marked as not implemented for meta backend in this table, which means that they will not yet work for any of the underlying backends.