heed VS tpr

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…

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?

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!

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

Have you considered heed or even sanakirja?

rkv hasn't been updated for a while. I recommend using heed - https://docs.rs/heed

For wrappers around LMBD, I'd recommend RKV or Heed https://github.com/mozilla/rkv https://github.com/Kerollmops/heed

Hey, this might interest you, as a similar thing could be implemented as bridge between freenet and the clearnet. I've been working on this for a while now. https://github.com/Alonely0/tpr

I'm throwing away all the code I had written and implementing my TPR protocol from scratch, I'll be using tower this time, lesson learned...

I'm more of a pomegranate guy

I'm implementing tpr, so I'll definitely take a look at this

Lariv is a thread-safe, self-memory-managed vector with no guaranteed sequential insert. It internally uses a linked ring buffer, that unlike traditional ring buffers, is growable, and very importantly, it doesn't reallocate the whole buffer as part of the process. It has been born inside the TPR project, and it is designed for storing client connections on TPR servers, which usually are short-lived data that have to be accessed via 128-bits integers. This is basically the dashmap for vectors.

In my case I use IDs for pairing multiplexed connections to encryption keys. I'm implementing The Pomegranate Router.