Pebble is equivalent to a table of a database in AOE engine, and the schema of the table has only one string column. Rocksdb with multiple column families is equivalent to a database with multiple tables in AOE, and each table has only one string column. An AOE engine can replace multiple Rocksdb instances, it can be virtualized into multiple KV engine.
Dependency
Support delete operation
In-memory index for search
Integrate some scan and filter operators
1275, #1276
KV APIs
Pros
One instance with unified memory | thread | io management
Unified engine for row and column-oriented workloads
Low overhead and IT operations compared to multiple stores
Share log with external WAL
Supports atomicity of cross-engine(row and column engine) operations
Support efficient data snapshot, split, relocation, installation
Cloud-native architecture. Log, data, and metadata are clearly layered and can be replaced with cloud-native components
XuPeng-SH
commented
2 years ago
Pebble is equivalent to a table of a database in AOE engine, and the schema of the table has only one string column. Rocksdb with multiple column families is equivalent to a database with multiple tables in AOE, and each table has only one string column. An AOE engine can replace multiple Rocksdb instances, it can be virtualized into multiple KV engine.