You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/04/27 12:52:04 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=15986550#comment-15986550 ] 

Nigel Jones commented on ATLAS-1757:
------------------------------------

I think this is important given the stagnant nature of the official titan code. It appears there's no changes since Dec 2015. We should have a well supported community driven graph DB as at least one option, and Janusgraph seems to fulfill that (and of course is titan compatible in any case). This will likely become more important as we drive the graph more, and continue pushing the scalability/enterprise capabilities of Atlas.

As to other graphDBs, I can't answer that particular angle other than suggest we do have a reasonable story for running Atlas standalone (outside hadoop) yet in a scalable manner. Given the use of titan currently the storage options are berkelyDB - fine for local sandpit, but not scalable, hbase - good for hadoop, but maybe less desirable outside, & cassandra - good for a highly scalable approach but harder to setup. Perhaps the use of a relational database(s) to back titan graph could be one option, using opensource db like postgressql, mariadb, and allowing customer option of a commercial db like db2, oracle, mssqlserver? For Janus that's more a wish for that community, but it does impact the Atlas user hence I mention it here :-)

> 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
>
> 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.3.15#6346)