sled VS heed

How do you compare this to sled? https://github.com/spacejam/sled

Sled uses bw-tree actually https://github.com/spacejam/sled/wiki/sled-architectural-outlook

There is a valid argument to be made for threads over async in a large percentage of use cases where async is considered the default. If this is what you are referring to however, I don't think they ever referred to async as completely useless: https://github.com/spacejam/sled/issues/1123.

Have you looked into other pure-Rust databases as well, such as sled or GlueSQL which has an SQL interface on top of sled? I wonder how those would compare to Persy.

I'm not sure what you need. Are these of any use? https://github.com/meilisearch/heed https://github.com/spacejam/sled

There is also Sled but as I understand it that is being reworked to use the author's new DB core Marble

There are some databases like sled/FlashDB designed to be embedded to other applications even bare metal microcontrollers. But I do doubt the potential bussiness value of a pure embedded database.

At Meilisearch we are currently trying to add a better error handling in heed v0.20, our LMDB key-value store wrapper. Unfortunately, when there are a lot of generics it can become harder to play with…

The big issue with compiling milli (meilisearch's rust search engine library) is that it uses LMDB. I noticed some possible smaller issues as well, but those can hopefully be worked out easily in the future. TL;DR: LMDB won't compile to WASI in the next few years, if ever. You need a WASM-friendly replacement. Looked into other options here but none are really suitable. Thus, only idea I could come up with is making a LMDB polyfill that uses IndexedDB under the hood for web support. See here: https://github.com/meilisearch/heed/issues/162. I plan on making a PR for it at some point but I have no clue when since it is a decently large feat. Side note: if you wanted to help, I would be happy to have it!

There are issues and pull requests but I advise you to look at the milli folder in the Meilisearch repository, it’s where all the logic is done. We extensively use RoaringBitmaps, heed the LMDB wrapper and grenad when indexing.

I’ll continue to introduce new features and new safety guards until v0.20.0. Can you tell me more about your project? Or is it private?

I'm not sure what you need. Are these of any use? https://github.com/meilisearch/heed https://github.com/spacejam/sled

LMDB support multiple readers and one writer at the same time. It is ensured by the library. Note that LMDB is a key-value store. You can use the heed library which is the most maintained Rust wrapper.

Note that heed is ensuring that you are not trying to use transactions, databases and environments in the right way. I have added much more work in that regard in the important update that I am working on too!

This rewrite will make heed based on the latest version of LMDB, the mdb.master3 branch. This version will also bring the new page-based encryption feature. I would be thankful if you could use it and tell me the issues you found.

I am currently working on exposing the new LMDB encryption feature from heed the safe LMDB wrapper with the help of the Cryptography community.