Using with Neo4j Causal Cluster
This chapter describes considerations around using Neo4j Connector for Apache Spark with Neo4j Enterprise Causal Cluster.
Neo4j Clustering is a feature available in Enterprise Edition which allows high availability of the database through having multiple database members.
Neo4j Enterprise uses a LEADER/FOLLOWER operational view, where writes are always processed by the leader, while reads can be serviced by either followers, or optionally be read replicas, which maintain a copy of the database and serve to scale out read operations horizontally.
Sometimes there will be remote applications that talk to Neo4j via official drivers, that want to use streams functionality. Best practices in these cases are:
Always use a
neo4j+s://driver URI when communicating with the cluster in the client application.
Was this page helpful?