9 ms·

I've been loosely following this: https://github.com/spacejam/sled https://github.com/spacejam/sled Since I'm writing in rust it might be a good fit. It's non

• pdimitar 7y ago
  Not to be a complete cynic but IMO you should just use any of the pretty well-done NoSQL K/V stores if you don't mind ditching SQL. There's plenty that are very well done, BoltDB successors and FoundationDB included. BTW I've heard very good things about the widely used sqlite Rust libraries (sorry, don't remember the names).
  • pedrocr 7y ago
    >Not to be a complete cynic but IMO you should just use any of the pretty well-done NoSQL K/V stores if you don't mind ditching SQL. My thought process is that the current solution works so I'd only change to a K/V store with the extra complexity if that got me a better API and more of the stack in Rust. Consuming something in Go seems like a pain, while also adding a GC runtime just for this. >BTW I've heard very good things about the widely used sqlite Rust libraries (sorry, don't remember the names). I'm using rusqlite, seems to work fine.
    • pdimitar 7y ago
      I wonder how a Rust library deals with the fact that sqlite is loosely typed.