| commit 3754fcb529ee028f59668f137ec78e2317452e74 |
| Author: Liang Zhang <zhangliang@apache.org> |
| Date: Fri Aug 12 12:57:28 2022 +0800 |
| |
| Update mode parts in deployment doc (#20110) |
| |
| diff --git a/docs/document/content/overview/deployment.cn.md b/docs/document/content/overview/deployment.cn.md |
| index 30a03beb34a..7f2d1d0b7da 100644 |
| --- a/docs/document/content/overview/deployment.cn.md |
| +++ b/docs/document/content/overview/deployment.cn.md |
| @@ -62,19 +62,18 @@ Apache ShardingSphere 是多接入端共同组成的生态圈。 |
| |
| ## 运行模式 |
| |
| -Apache ShardingSphere 是一套完善的产品，使用场景非常广泛。 |
| -除生产环境的集群部署之外，还为工程师在开发和自动化测试等场景提供相应的运行模式。 |
| -Apache ShardingSphere 提供的 2 种运行模式分别是单机模式和集群模式。 |
| +Apache ShardingSphere 提供了两种运行模式，分别是单机模式和集群模式。 |
| |
| ### 单机模式 |
| |
| 能够将数据源和规则等元数据信息持久化，但无法将元数据同步至多个 Apache ShardingSphere 实例，无法在集群环境中相互感知。 |
| 通过某一实例更新元数据之后，会导致其他实例由于获取不到最新的元数据而产生不一致的错误。 |
| + |
| 适用于工程师在本地搭建 Apache ShardingSphere 环境。 |
| |
| ### 集群模式 |
| |
| 提供了多个 Apache ShardingSphere 实例之间的元数据共享和分布式场景下状态协调的能力。 |
| -在真实部署上线的生产环境，必须使用集群模式。 |
| -它能够提供计算能力水平扩展和高可用等分布式系统必备的能力。 |
| -集群环境需要通过独立部署的注册中心来存储元数据和协调节点状态。 |
| +它能够提供计算能力水平扩展和高可用等分布式系统必备的能力，集群环境需要通过独立部署的注册中心来存储元数据和协调节点状态。 |
| + |
| +在生产环境建议使用集群模式。 |
| diff --git a/docs/document/content/overview/deployment.en.md b/docs/document/content/overview/deployment.en.md |
| index d24d2725261..f348dd2e68a 100644 |
| --- a/docs/document/content/overview/deployment.en.md |
| +++ b/docs/document/content/overview/deployment.en.md |
| @@ -61,21 +61,23 @@ By combining ShardingSphere-JDBC and ShardingSphere-Proxy, and using the same re |
| |
|  |
| |
| -## Operation Modes |
| +## Running Modes |
| |
| -Apache ShardingSphere is a complete set of products applicable to a wide range of usage scenarios. |
| -In addition to the cluster deployment of the production environment, it also provides corresponding operation modes for engineers in the development process and automated testing scenarios. Apache ShardingSphere provides two runtime modes: standalone mode and cluster mode. |
| +Apache ShardingSphere provides two running modes: standalone mode and cluster mode. |
| |
| ### Standalone mode |
| |
| -It can achieve data persistence in terms of metadata information such as data sources and rules, but it is not able to synchronize metadata to multiple Apache ShardingSphere instances or be aware of each other in a cluster environment. |
| +It can achieve data persistence in terms of metadata information such as data sources and rules, |
| +but it is not able to synchronize metadata to multiple Apache ShardingSphere instances or be aware of each other in a cluster environment. |
| Updating metadata through one instance causes inconsistencies in other instances because they cannot get the latest metadata. |
| + |
| It is ideal for engineers to build a ShardingSphere environment locally. |
| |
| ### Cluster mode |
| |
| It provides metadata sharing between multiple Apache ShardingSphere instances and the capability to coordinate states in distributed scenarios. |
| -In an actual production environment for deployment and release, you must use the cluster mode. |
| |
| It provides the capabilities necessary for distributed systems, such as horizontal scaling of computing capability and high availability. |
| Clustered environments need to store metadata and coordinate nodes' status through a separately deployed registry center. |
| + |
| +We suggest using cluster mode in production environment. |
