It's true that LevelDB has a lot of drawbacks, including its complexity (making reliability problems much more likely). However, I think Howard Chu is way too p

It's true that LevelDB has a lot of drawbacks, including its complexity (making reliability problems much more likely). However, I think Howard Chu is way too pessimistic about (I'd say biased against) LSM-trees. I wrote an LSM-tree database based on Chu's LMDB[1] that was able to support a much higher write throughput than LMDB, although it was still slower than LevelDB for writes. Unfortunately it had some other drawbacks and would be hard to make it "production ready" so I'm not using it. I'm using LMDB by default in my current project because of it's simplicity and read performance (which are truly amazing). But I'm convinced that a write-optimized database on par with LMDB is possible. SQLite4[2] might eventually be it, if it ever gets finished. [1] https://github.com/btrask/lsmdb https://github.com/btrask/lsmdb [2] https://www.sqlite.org/src4/doc/trunk/www/lsmusr.wiki https://www.sqlite.org/src4/doc/trunk/www/lsmusr.wiki