atlas-dev mailing list archives

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


Nigel Jones commented on ATLAS-1757:

Interesting info Dougal :-) ... on the license Apache specifically have an issue with the
revocation option... I found Simon Phipps blog informative, but clearly it's the apache pmcs,
and apache legal that would have to make any call on what's allowed/not-allowed. for now though
react is a problem. More at
. As an aside a quick glance at the graphQL java libraries suggest they are MIT licensed so
not an issue.

I'm not an expert on graph, or graph libraries... from my uninformed (!) perspective Tinkerpop
has significant attraction in being an open apache project, with meritocratic governance -
I'm not sure that graphQL is in that same space?

> 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