graph-databases

I am exploring JanusGraph DBs and require visual editing, like MySQL workbench. I found some visual editors for Neo4j . Are there any visual editors for JanusGraph as well? or can those tools be used with JanusGraph? Per JanusGraph's README : To visualize graphs stored in JanusGraph, you can use any of the following tools: Cytoscape Gephi plugin for Apache TinkerPop Graphexp KeyLines by Cambridge Intelligence Linkurious 来源： https://stackoverflow.com/questions/47254804/gui-for-building-janusgraph-db

i wonder wether there is a solution (or a need for) an ORM with Graph-Database (f.e. Neo4j). I'm tracking relationships (A is related to B which is related to A via C etc., thus constructing a large graph) of entities (including additional attributes for those entities) and need to store them in a DB, and i think a graph database would fit this task perfectly. Now, with sql-like DBs, i use sqlalchemyś ORM to store my objects, especially because of the fact that i can retrieve objects from the db and work with them in a pythonic style (use their methods etc.). Is there any object-mapping

I've been playing with Titan graph server for a while now. And my feeling is that, despite an extensive documentation, there is a lack of Getting started from scratch tutorial . My final goal is to have a titan running on cassandra and query with StartTheShift/thunderdome . I have seen few ways of starting Titan: Using Rexster from this link , I was able to run a titan server with the following steps: download rexster-server 2.3 download titan 0.3.0 copy all files from titan-all-0.3.0/libs to rexster-server-2.3.0/ext/titan edit rexster-server-2.3.0/rexster.xml and add (between a ): <graph>

Recently I have been looking into graph databases like Neo4j and into logic programming in Prolog and miniKanren. From what I have learned so far, both allow specifying facts and relations between them, and also querying the resulting system for some selections. So, actually I cannot see much difference between them in that they both can be used to build a graph and query it, but using different syntax. However, they are presented as totally different kinds of software. Except the technicality that databases maybe propose a more space-time effective storage technology, and except that tiny

What's currently the best choice to persist graph-like structures? Graph databases (e.g. Neo4j ) or RDF triple stores (e.g. Virtuoso )? For example, we have the following use case: the weakly connected graph (similar to the one of scholarly papers in a collection) with nearly 10M nodes; quite rare updates; critical operations: retrieving particular sub-graphs, updating nodes in a given sub-graph, re-computing link analysis measures (e.g. HITS or PageRank) after updating some nodes. Providing the standard API to query the data for third party applications (a la Facebook's or Twitter's) is