Move all operations to Neo4j 2.0 based cypher endpoint

aseemk / node-neo4j-template

A template app for using Neo4j from Node.js.

http://node-neo4j-template.herokuapp.com/

216 stars 92 forks source link

Move all operations to Neo4j 2.0 based cypher endpoint #16

Closed jexp closed 10 years ago

jexp commented 10 years ago

Like Peter and I did here: https://github.com/neo4j-examples/node-neo4j-template

That would be awesome!

aseemk commented 10 years ago

Thanks @jexp. I'll move this issue to the driver repo.

FWIW though btw, in some quick local benchmarking we had done earlier at FiftyThree, if we use the REST format (which the driver relies on today), the new endpoint is no faster than the old one — and in fact it's sometimes slower!

aseemk commented 10 years ago

https://github.com/thingdom/node-neo4j/issues/138

jexp commented 10 years ago

That might be and will change with the new query planner, but having transaction isolation and the ability to bundle statements imho outweighs that.

aseemk commented 10 years ago

Agreed that having the foundation to bundle multiple query statements is the major benefit, but could you clarify the other two things?

Aren't individual queries sent through /db/data/cypher also isolated / run transactionally?
Would query planner updates not apply to queries sent through /db/data/cypher too?

Thanks Michael!