Best way to add support for a new KV backend store


#1

Hi

I’m considering the idea to add support for a new backend (somewhere between KV and nosql) and I’m looking for best practice to save the quad in either case.
what is the most efficient way to save a quad in a KV store ? or in a nosql one ?

I couldn’t find a documentation on this topic, sorry if it already exist.

Thanks
Damien


#2

Sorry for the late reply.

The higher is the abstraction layer of the database, the better, in general. If you still consider adding the backend, please take a look at this project. We are slowly transitioning Cayley to use it.