[
https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093035#comment-16093035
]
Dougal Watt commented on ATLAS-1757:
------------------------------------
Interesting point David. GraphQL isn't in the FB open source projects library,
but is published as a specification. There are many reference implementations
that use the spec. My company will likely use a Java Client (here's one under
MIT license: https://github.com/graphql-java/graphql-java), and build the
server we need for Blazegraph (under the covers it will parse the query and
convert to SPARQL). So as I read it, the spec is just the spec, it's up to the
end user to create the client and server implementations of the spec and
license them as they want.
> 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)
