Neo4j临时集群在高可用性集群上的优势 [英] Neo4j Casual Clustering benfits over High-Availability Clustering

问题描述

我们正在将HA集群迁移到因果集群.

We are in the process of migrating HA cluster to Causal Clustering.

从HA群集迁移到因果群集是否有真正的优势?

当前仅使用REST端点.

Currently using REST End points only.

是否可以仅使用两个Neo4j实例进行因果聚类?

谢谢.

推荐答案

因果群集是Neo4j群集的新一代，并且它将随着新版本的发展而不断发展.

Causal cluster is the new generation of Neo4j cluster, and it will continue to evolve with new releases.

与HA相比，CC有很多优点:

There are many advantages for CC comparing to HA :

• 没有分支数据(感谢木筏和共识提交)
• 更高的稳定性
• 具有螺栓协议的智能驱动程序(具有LB和read your own write功能)
• 集群通信加密
• ...

• no branch data (thanks to raft and consensus commit)
• more stability
• smart driver with bolt protocol (with LB and read your own write functionnality)
• cluster communication encryption
• ...

您至少需要 3个核心节点来创建集群(2n+1实际上，其中n是您要支持的故障数).

You need at minima 3 core nodes to create a cluster (2n+1 in fact where n is the number of failure you want to support).

我真的建议您使用bolt协议而不是REST API，因为官方驱动程序仅使用bolt，并且它们可以向您隐藏集群的复杂性.

I really recommend you to use the bolt protocol instead of the REST API, because official drivers only use bolt, and they can hide to you the complexity of a cluster.

这篇关于Neo4j临时集群在高可用性集群上的优势的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！