no_std LSM-tree with PAX blocks and ECC
StorageComments
The focus on reliability is encouraging. I wonder if the ECC overhead might impact write amplification on the very constrained systems this is targeting.
defra's rego just dropped an acid lsm and it is also rust.
If Rego already provides an ACID LSM in Rust, would the specific advantages of PAX blocks be enough to move a project over to coordinode?
Why do we need another Rust LSM? Is the PAX layout actually a game changer or just a niche optimization?
The ECC is the real winner here. We've had too many flash modules fail in the field due to bit rot, so having self-healing at the engine level is a practical necessity.
The PAX layout is a clever middle ground. By grouping columns within a single block, it minimizes cache misses during scans without the extreme fragmentation seen in pure columnar stores.