Using with Neo4j 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 Primary/Secondary servers operational view. Write operations are always processed by the Primary servers only, while reads can be serviced by either Primary servers (Leaders or Followers), or optionally by Read Replicas, which maintain a copy of the database and serve to scale out read operations horizontally.
Sometimes there are 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?