2 ms·
When you consider SQLite, you might want to get around SQL for impedance and performance reasons. There is a robust and decently fast key/value store in the bac
by Rochus 4mo ago
When you consider SQLite, you might want to get around SQL for impedance and performance reasons. There is a robust and decently fast key/value store in the backend. I used it in some of my projects (e.g. https://github.com/rochus-keller/udb https://github.com/rochus-keller/udb used e.g. in https://github.com/rochus-keller/crossline/ https://github.com/rochus-keller/crossline/). Depending on read/write frequency, lmdb or tidesdb might be a better fit.
- NuclearPM 4mo agoThis is cool. I wonder if WASM would work here as a target for the k/v store.