[
https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988499#comment-15988499
]
Graham Wallis commented on ATLAS-1757:
--------------------------------------
There are quite a few graph databases that might be worthy of consideration. I
think it is reasonable to suggest that we limit our attention to those that
have Apache-2 licensed APIs and that include support for Tinkerpop 3.2. The
latter restriction appears to eliminate ArangoDB, OrientDB and Gaffer but
leaves JanusGraph and Neo4j as candidates. JanusGraph is the more obvious
candidate as it is Apache-2 licensed throughout and (as noted in the articles
linked above) could be considered to be the reference implementation of TP3.
Whilst less obvious, Neo4j includes an Apache-2 licensed API library -
neo4j-gremlin - that does not include the GPL3-licensed implementation of
neo4j. We could adopt the above as our forward-looking strategy but I would be
keen that we chip away at this - e.g. by adding JanusGraph via the graph
abstraction layer and (at some point) making it the default and deprecating the
use of Titan 0 and Titan 1. Other graph databases (e.g. neo4j-gremlin) could be
added via the graph abstraction layer depending on users' requirements.
> 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)
