ppom
@ppom@mamot.fr  ·  activity timestamp last week

For the needs of #reaction, I wrote a very dumb #Rust#KV db which wraps BTreeMaps and a redis-like log file for persistance.
It's orders of magnitude faster than common KV #database (heed/lmdb, fjall, sled) because it's RAM-first.
But it doesn't have transactions, and it persists write operations asynchronously, after the write is done.
Those features make a lot of sense for reaction imo, but I don't know if it would be useful to others.

Question is: should I publish it as a separate crate?
ppom
@ppom@mamot.fr  ·  activity timestamp last week

For the needs of #reaction, I wrote a very dumb #Rust#KV db which wraps BTreeMaps and a redis-like log file for persistance.
It's orders of magnitude faster than common KV #database (heed/lmdb, fjall, sled) because it's RAM-first.
But it doesn't have transactions, and it persists write operations asynchronously, after the write is done.
Those features make a lot of sense for reaction imo, but I don't know if it would be useful to others.

Question is: should I publish it as a separate crate?