search

ninjudd / jiraph

A graph database with pluggable backends, written in Clojure.
Eclipse Public License 1.0
137 stars 15 forks source link

change DB to kyoto cabinet #12

Closed boxxxie closed 12 years ago

boxxxie commented 12 years ago

The tokyo cabinet site recommends using kyoto cabinet (the successor of toyko cabinet). http://fallabs.com/kyotocabinet/

ninjudd commented 12 years ago

My understanding is that Kyoto cabinet is two times slower than Tokyo cabinet. However, if you'd like to write a Masai db backend for Kyoto, then users could decide which to use.

Masai is located at http://github.com/flatland/masai, and is key value store library that backs the primary Jiraph implementation.

On Jun 24, 2012, at 9:18 AM, boxxxiereply@reply.github.com wrote:

The tokyo cabinet site recommends using kyoto cabinet (the successor of toyko cabinet). http://fallabs.com/kyotocabinet/

Reply to this email directly or view it on GitHub: https://github.com/flatland/jiraph/issues/12

Raynes commented 12 years ago

From what I've read, the whole "kyoto is successor" thing is just a marketing strategy. They're also under different licenses with kyoto being under GPLv3 which tends to make it less useful for commercial products.

With that said, Jiraph is designed to support whatever storage backend you want. If you want kyoto, you likely wouldn't have much trouble at all putting together a masai backend for kyoto and then you could make use of it with Jiraph's masai layer.

boxxxie commented 12 years ago

I read a bit more into this, and I wasn't able to find any recent comparisons between the two. However a lot of people have given kyoto bad press... pretty crazy stuff...

ninjudd commented 12 years ago

Going to close this. Please open an issue on Masai if you decide to implement a Kyoto backend.