Since I'm writing in rust it might be a good fit. It's non-SQL but does have some nice features. I would need to figure out how to adapt all the syncer features to that model though. Right now I should just focus on finishing the merging code to be able to release a 1.0 some time soon.
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).
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.