[
https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092891#comment-16092891
]
David Radley commented on ATLAS-1757:
-------------------------------------
[~dougal_watt] Interesting - I do not know anything about this project. I am
wondering about the license around this facebook open source. Apache has
recently said no to react.js
https://www.theregister.co.uk/2017/07/17/apache_says_no_to_facebook_code_libraries/
. I like Tinkerpop, as it is an open standard - I am not sure how open GraphQL
is; is this something that Facebook would be willing to contribute to the Atlas
code base for the Atlas community to assess?
The Atlas DSL and the new facetted search do provide structured queries (json
in json out) . I agree RDF is very powerful - though RDF and Owl may not be for
the faint hearted; so excludes (many) people who may not be willing to embrace
the steep learning curve involved.
We are also looking at GaianDB as part of the VDC project. This is an open
source project that exposes heterogeneous data sources over SQL.
> 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
> Attachments: ATLAS-1757 Proposal to change graph database.pdf
>
>
> 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.4.14#64029)
