Status: IN
Both storage paradigms in the reference implementations exhibit fundamental scalability constraints: the hash index requires all keys in RAM (making dataset size directly bound by available memory with no spill-to-disk fallback), while the LSM tree scans every SSTable on negative lookups because the correctly-implemented Bloom filter module is never wired into the read path.
hash-index memory bound + LSM missing-key linear scan = neither paradigm scales gracefully
Depends on (SL): hash-index-is-memory-bound-by-design, lsm-miss-probes-all-due-to-no-bloom-integration