atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dougal Watt (JIRA)" <>
Subject [jira] [Commented] (ATLAS-1757) Proposal to update graph DB
Date Wed, 19 Jul 2017 09:32:02 GMT


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 ( 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:
>             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

View raw message