rasgueadb VS syn

I experimented with ObjectBox a bit, but I decided against using it because it isn't open source. The language wrappers are apache2 but the core library is only provided as a binary blob. I think this is bad because you can't inspect how it works, fix bugs, port it to new archs, integrate it fully into your build system, etc. Also, every cursor operation must call into their function entry points (as opposed to being inlined in your code for example).

Instead, I've been working on my own library which also uses LMDB and flatbuffers. It's C++ only and still a WIP, but in case anyone else is interested, it's here: https://github.com/hoytech/rasgueadb

hey so i messaged someone on the Holo team (Paul d'Aoust @helioscomm), this was his reply:

Yes, people will want conflict-resolution for contention on scarce resources, and it'd be lovely to have that baked into the system. Two options (and yes, both still leave conflict resolution in the app dev's hands):

- Have the zome function resolve the conflict after it retrieves conflicting metadata from the DHT

- In the future we'll bake conflict resolution right into the network layer, so DHT authorities can resolve the conflict automatically using CRDTS or manually by pinging the nodes that published conflicting information so they can resolve it themselves.

It's also worth mentioning Syn, a library which uses operational transforms (a precursor to CRDTs) for conflict-free collaborative document editing. https://github.com/holochain/syn I'm looking forward to seeing someone produce something similar, but with CRDTs.