If you're using spring you can also look into Spring Data Neo4j (http://spring.neo4j.org)
(see the docs here: http://static.springsource.org/spring-data/data-graph/snapshot-site/reference/html/#reference:neo4j-server) and its use of the SpringRestGraphDatabase and/or the java-rest-binding (https://github.com/neo4j/java-rest-binding). You could also add a domain level server-extension to the neo4j server that talks a application specific protocol (instead of the generic REST protocol). The best way is to do a PoC for your use-case(s) and measure the ease of use + performance for your domain model + data. Haven't seen the "RESTDataService" you referenced, do you have any docs on that? Cheers Michael Am 17.11.2011 um 14:34 schrieb Vinicius Carvalho: > Hi there! I've being playing around with neo4j for a few weeks now. I'm > using embedded graph db, and the data lives inside my developer machine. > But now I need to turn things into a more production like stage. > > Coming from a traditional SQL world where we have our clusters of DB > running in some servers and all AppServers accessing remotely via jdbc > connections. I'm wondering what is the best approach with neo4j? > > Is REST the way to go when we have a separation from AppServers and the > node servers? I've seen some ppl saying that one could use HA and have DBs > collocated on each machine and have the HA capabilities to sync the > storage, but I'd like to avoid this approach at all, we don't want to have > graphdb servers and appservers on the same machine (not my call this > decision unfortunately) > > It seems to me that Spring has some nice RESTDataService that wraps the > REST API, so I'm considering going that way. > > Just wondering what would be a recommend strategy for this. > > Regards > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
