Kynao, Neo4j HA is right now a multiple slaves - single write master architecture that will have a write guarantee on 2 nodes if you write to a slave - the slave itself and the master.
While this is good and stable for failover and read-heavy production scenarios, in the next version of Neo4j (2.x) we are looking at actually sharding the graph more dynamically than a Dynamo ring, especially runtime, on different machines, so we kind of hop over the stage of having configurable guarantees in a dynamo replication cluster in order to reach the dynamic graph sharding stage faster. HTH? 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 Wed, Sep 14, 2011 at 11:08 AM, Kynao <[email protected]> wrote: > Hi, > > I'm interested by the "Multi-master" feature like explained here > http://www.assembla.com/spaces/orientdb/wiki/Multi-master_server_architecture. > i'm also interested to discuss this proposition... > > What do you think ? > What re you remarks ? > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Multi-master-server-architecture-tp3335268p3335268.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.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
