Deno KV: consider using LMDB instead of SQLite for local

[alexgleason]

LMDB is embedded like sqlite, is already a key-value store instead of a relational database, and is much faster in benchmarks: https://github.com/kriszyp/lmdb-js

[alexgleason]

The author of lmdb-js thinks this is a good idea. The databases are nearly 1:1 according to him: kriszyp/lmdb-js#236 (comment)

sqlite seems like kind of a hack for local dev. Backing it with lmdb would make self-hosted Deno KV suitable for production workloads.

[bartlomieju]

CC @losfair

[xyzshantaram]

Hi all, I've started working on this in a personal fork of Deno (it's very barebones for now). I'm building a new KV backend implementation that will slot in alongside the existing SQLite and remote implementations.

@bartlomieju @losfair Would you guys be interested in merging something like that? I'd like to know before I continue working on it because forking would (obviously) not be feasible for me and I'd rather just do it as an FFI lib if it's not going to end up inside Deno.

https://github.com/xyzshantaram/denokv_lmdb is where it's at, it's very early stages at the moment.

[bartlomieju]

@xyzshantaram could you please open an issue about it to discuss in more detail?

[xyzshantaram]

Opened #23545, please have a look at your convenience. Thank you!