Sunday, 15 February 2015

Proper way to store graphs with Neo4J -



Proper way to store graphs with Neo4J -

i'm building scheme allows user phone call n number of different graphs through api. have working prototype pulls graphs couchdb. however, obvious reasons, move graph db. understanding neo4j can handle 1 graph @ time or requires sort of tagging scheme not mix graphs. neither of approaches seem optimal. what's best practice approach this?

a few more things note: calling these graphs , manipulating them networkx, , i've considered storing graphs in "regular" db moving them neo4j requests come in, seems pretty intense.

neo4j not have concept of multiple databaseslike relational databases using create database. in neo4j there 1 graph space can use.

so have 2 options:

use seperate neo4j instances (single or clustered) each graph, maybe using neo4j in embedded mode helpful here use 1 neo4j instance (single or clustered) , store info in distinct subgraphs. if subgraphs need interconnections can utilize labels identify subgraph node belongs.

graph neo4j couchdb

No comments:

Post a Comment