Hi Stefan, > 1. Is the REST API the only way to use the server?
Right now, yes. We have plans for a binary protocol interface and native language bindings in the future however (or you could write your own). Anecdotally it seems that you lose one order of magnitude of performance with the REST API compared to embedding directly in the JVM, which isn't too bad. > 2. Is the REST API ready for production usage? Yes we have earlier versions of the REST API in production, but there caveats. For example, if you create *really* huge traversals then you'll slow things down considerably. > > 3. Is there a higher level API to access the REST > server than described here: > > http://components.neo4j.org/neo4j-examples/snapshot/server-rest-api.html No, that *is* our REST API. It's even hypermedia friendly. But point taken that our documentation could be improved. > 4. Is there a "standard" style/examples to bridge the gap > between database and business logic? (daos?) The simplest approach I've observed is to implement the storage part of your domain objects using graph nodes rather than native fields. Then you wrap your behaviour around that node - a reasonable separation of state and behaviour. Hope that helps a bit. Jim _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
