Hi Phillipe, thanks for your precious reply. I'm actually thinking that in general we should decide whether to discard or use Object Graph Mapping modelling more or less the same way we decide to use Hibernate (or a similar Object Relational Mapping) in the relational world: automatic mapping between my object domain model and the database sounds useful, don't you agree? (tons of Node.getProperty + MyDomainObj.setProperty saved). Hibernate also solves object-relational impedance mismatch, but with a graph database this comes for free.
Furthermore, for companies - as my own one - that use to develop applications using the Spring Framework, Spring Data Neo4j (not necessarily the OGM part) seems a natural solution when introducing a graph database. Any feedback appreciated! :) Thank you again! Lorenzo Il giorno lunedì 17 marzo 2014 21:04:32 UTC+1, Philippe Baumard ha scritto: > > @Lorenzo Speranzoni >> > > Hi, > I am developping an application with Noe4j (www.bontirage.com). > I was surprised by the number of possibilities to use Neo4j. > - Embedded, > - REST API, > - Cypher, > - Sprind Data, > > What to do? > i did research about the performance i my choice was Embedded Database > with API. > > I disapprouve completely Sping Data Neo4j. > Because of the performance, and the versions updates too slow. > > Cypher is a marvelous language but i don't think it is the tools for a > large number of connections. > > -- 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.
