[ https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986970#comment-15986970 ]
Ashutosh Mestry edited comment on ATLAS-1757 at 4/27/17 4:36 PM: ----------------------------------------------------------------- With some digging, I came across this [article|https://www.datanami.com/2017/01/13/janusgraph-picks-titandb-left-off/]. JanusGraph comes close since it is a fork from TitanDB. What about [Neo4J|https://github.com/neo4j/neo4j]? It is licensed under GPLv3. was (Author: ashutoshm): With some digging, I came across this [article|https://www.datanami.com/2017/01/13/janusgraph-picks-titandb-left-off/]. JanusGraph comes close since it is a fork from TitanDB. What about [Neo4J|https://github.com/neo4j/neo4j]. It is licensed under GPLv3. > Proposal to update graph DB > --------------------------- > > Key: ATLAS-1757 > URL: https://issues.apache.org/jira/browse/ATLAS-1757 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Affects Versions: trunk > Reporter: Graham Wallis > > Given the formation of the JanusGraph open source project (under the Linux > Foundation) to continue the development and support of the Titan DB, should > we aim to deprecate Titan and move over to JanusGraph? > If we did this, we could keep the graph abstraction layer and use it to > support Titan 0, Titan 1 and JanusGraph. > Are there other graph databases that we should consider? -- This message was sent by Atlassian JIRA (v6.3.15#6346)