Choice between REST API or Java API -

Choice between REST API or Java API -

i have been reading neo4j lastly few days. got confused whether need utilize rest api or if can go java apis.

my need create millions of nodes have connection among them. want add together indexes on few of node attributes searching. started embedded mode of graphdb java api reached outofmemory indexing on few nodes thought improve if neo4j running service , connect through rest api memory management swapping in/out info underlying files. assumption right?

further, have plans scale solution billion of nodes believe wont possible single machine's neo4j installation. believe neo4j has capability of running in distributed mode. reason thought continuing rest api implementation best idea. though couldn't find out documentation how run neo4j in distributed environment.

can stuff batch insertion, etc. using rest apis well, java apis graph db running in embedded mode?

do know why getting outofmemory exception? sounds creating these nodes in same transaction, causes live in memory. seek committing little chunks @ time, neo4j can write disk. don't have manage memory of neo4j aside things cache.

distributed mode in master/slave architecture, you'll still have re-create of entire db on each system. neo4j efficient disk storage, node taking 9 bytes, relationship taking 33 bytes, properties variable.

there batch rest api, grouping many calls same http call, making rest calls still slower if embedded.

there disadvantages using rest api did not mentions, , that's stuff transactions. if going atomic operations, need create several nodes, relationships, alter properties, , if step fails not commit of it, cannot in rest api.

java api rest scalability neo4j