ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

Neo4j High Availability Cluster

Neo4j uses the Master-Slave replication model. All writes must go through the master and the slaves will be read only. Changes performed on the master will be pushed out to the slaves when the logical log is rotated (based on configured size or invoking a method on the master).

The online backup utility used to synchronize a destination Neo4j database from a source Neo4j database can be used to emulate “high availability” (HA) having the master replicating changes to read only slaves.

I didn’t know Neo4j supports a highly available setup. Since when?[1]


  1. The ☞ official documentation mentions as last modification time Oct. 22nd.  ()

Original title and link: Neo4j High Availability Cluster (NoSQL databases © myNoSQL)