You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Dougal Watt (JIRA)" <ji...@apache.org> on 2017/07/19 09:32:02 UTC

[jira] [Commented] (ATLAS-1757) Proposal to update graph DB

    [ https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092850#comment-16092850 ] 

Dougal Watt commented on ATLAS-1757:
------------------------------------

The state of integration for graph DB's is somewhat in flux, with Tinkerpop being more oriented towards analytics use cases than straight out integration. For the latter, GraphQL is proving to be a very nice solution (graphql.org). It's a query language and information-centric API rolled into one, and both the query syntax and outputs are structured in the same way. Nicely, the query return is in JSON format, so everything on the upstream side of the API can be totally standard internet technologies. The architecture of GraphQL also allows for integration of any back end data store so you can have more than one, pluggable databases behind the scenes.
I've started two companies building SaaS products on top of graph DB's, and choose Blazegraph due to it's support for RDF and GPU acceleration. An RDF graph would allow Atlas to define the required metamodel in RDF and use it to reason over instance data received and send by Atlas between different data lakes - you'd also get metamodel validation and conformance, and a highly evolvable schema.

> 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)