By Aileen Agricola | January 31, 2018
In 2017 Neo4j took yet another important step in improving the flexibility and scalability of graphs in production. In years past, running a highly available Neo4j database cluster allowed you to easily distribute reads across the cluster, but required all writes to be sent to a single node. Whereas other NoSQL databases support distributed writes by sacrificing ACID Transactions serializability, the creators of Neo4j refused to relax those guarantees. The goal was always to provide an enterprise-grade consistent, reliable source of truth.