Hi Bo,

If you do naive traversals with the REST API (traversing one relationship per 
HTTP request), it'll be an order of magnitude slower than the Java API because 
of the network overhead. That's because the default REST API is intended for 
exploration (at human scales) rather than transaction processing.

However the REST API can easily be augmented with unmanaged extensions. This 
means you get to write your Java code as per usual and host is in the Neo4j 
server. Your code then sits between the database and the Web: on one side you 
have the regular Java APIs to code against with the database, and on the other 
side you have JAX-RS to map back to the network. This means you're working at 
the same level/speed as the Java API because you are using the Java API.

Still, before you do any of that you really should check out the Cypher 
endpoint. If you can do your work in Cypher, it'll be far more pleasant.

Jim

-- 
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.

Reply via email to