Cayley – An open-source graph database
github.com
Cayley – An open-source graph database
1–10 of 60 posts
Re: Cayley – An open-source graph database
#2Re: Cayley – An open-source graph database
#3The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
Re: Cayley – An open-source graph database
#4The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
Re: Cayley – An open-source graph database
#5The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
Re: Cayley – An open-source graph database
#6The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
Re: Cayley – An open-source graph database
#7Interesting location, being in the main Google organization, given this disclaimer. I've seen other projects with this disclaimer under Googlers' personal pages before, and I always figured a /google/ URL probably meant it was officially a Google project.
Re: Cayley – An open-source graph database
#8The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
Cayley's codebase is not large and very clean.
Re: Cayley – An open-source graph database
#9The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
there is also: https://github.com/dgraph-io/dgraph also a golang project as the title mentions, if this matters to anyone.
Re: Cayley – An open-source graph database
#10The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
http://orientdb.com/orientdb/
asking because i've looked at it a couple of years back and decided to go with SQL but the project looked reeeaally interesting back then and it still might fit for new development.