Duncan, the neo4j-rest-binding was built before Cypher was invented, and before the transactional endpoint was introduced. As such, it generally uses the CRUD operations exposed by Neo4js REST API, and it implements the Core Java API which the original Neo4j Embedded did (and still does). Unfortunatly, while the embedded API is very fast when run in-process, it is not a very suitable API to use over the network. The REST API also does not expose long-running transactions.
As such, the JDBC API was built, and uses Cypher only and (in the latest version) the new transactional endpoint. This means that for every network hop incurred, it performs much more work by virtue of sending a full Cypher query rather than a REST CRUD call. It also means it's generally faster, because the transactional endpoint is faster, and it means it allows keeping a running transaction and reading intermediary results. Eg. if you are starting a new project in Java, I would recommend JDBC. That said, it's not an official Neo4j component, it's a community managed project. /jake On Wed, Apr 2, 2014 at 12:09 AM, BtySgtMajor <[email protected]> wrote: > Hi all, > > Given that both the Java REST binding and the JDBC drivers are available > (both of which can communicate w/ a Neo4j server via REST), besides the > usage/familiarity with them, what are the real differences/pros/cons > between the two, if any at all? I've been going through both and am > curious. > > Michael Hunger, maybe you could weigh in? > > Cheers, > Duncan > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
