http://docs.neo4j.org/chunked/snapshot/rest-api-batch-ops.html
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Sun, Jun 19, 2011 at 7:46 PM, Mattias Persson <[email protected]> wrote: > 2011/6/19 Jim Webber <[email protected]> > >> Hello Aniceto, >> >> > - EmbeddedGraphDatabase, which is good for tests, supports transactions >> > and has quick communications. Not good for medium sized or HA apps >> > because lacks separation between app and data >> >> The EmbeddedGraphDatabase is fine for production use - in fact it's the >> default choice! The difference between using an EmbeddedGraphDatabase and >> the REST API is where the instance of EmbeddedGraphDatabase resides. If you >> use the REST API, it lives in our server process, otherwise it lives in your >> process. >> >> Really the distinction is much less than that names imply. >> >> > - standalone server: data repository is set apart from application, even >> > more than one app can access it. If EE, HA is available, but has a REST >> > interface which does not support transactions >> >> It has transactions of course - Neo4j is *always* ACID transactional. But >> this interface does not expose those transactions to users. Instead a >> transaction is implicitly wrapped around every interaction. >> >> > Can we expect any new communication interface with TX and HA support for >> > standalone servers, at least for Java/JVM clients or has the roadmap >> > another target? >> >> HA is supported whether you choose to use Neo4j embedded within your >> process or whether its embedded within our process inside the REST API. >> >> We're starting to think about next generation protocol support. That will >> probably include transactional control on the client side, but we have >> nothing to release in the 1.4 timeframe. >> > > Apart from the fact that you can send "batch operations" to the REST API, > i.e. group a number of operations to be executed in one transaction, instead > of one by one. This has the benefint of those operations being atomically > applied and much faster as well due to less http requests and also less > transactional overhead (commiting each transaction has some overhead > otherwise). Maybe someone could supply a good link for further information > since I don't really have any. > >> >> Jim >> _______________________________________________ >> Neo4j mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user >> > > > > -- > Mattias Persson, [[email protected]] > Hacker, Neo Technology > www.neotechnology.com > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
