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 13:19:00 GMT


Dougal Watt commented on ATLAS-1757:

Hi Nigel, good to see you online again! Tinkerpop is a great system, especially in how it
abstracts the db and sits across OLAP and OLTP use cases, and it's strong governance, which
GraphQL lacks. There are sometimes wrinkles in how graph db's support it though e.g. Blazegraph
doesn't enable it for full HA clustered configurations. 
The really nice thing with GraphQL is you get back JSON so it's very accessible for developers,
and the type system, mutations, introspection and validation are all very easy to use, and
directly resemble the query system so it's very easy to understand.
If all you need to do is support transactional processing (and my companies are using it for
a whole range of businesses) then it's likely easier to use from a development perspective
than Tinkerpop.

> 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