This is an automated email from the ASF dual-hosted git repository. zhaojinchao pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push: new 639b5ec39ea delete memory mode (#19908) 639b5ec39ea is described below commit 639b5ec39ea4923d1a12d1d74b2932018723294a Author: Mike0601 <40025573+mike0...@users.noreply.github.com> AuthorDate: Fri Aug 5 20:15:16 2022 +0800 delete memory mode (#19908) --- docs/document/content/overview/mode.cn.md | 10 +++------- docs/document/content/overview/mode.en.md | 10 +++------- docs/document/static/img/overview.cn_v2.png | Bin 57565 -> 57011 bytes docs/document/static/img/overview.en.png | Bin 60769 -> 60751 bytes 4 files changed, 6 insertions(+), 14 deletions(-) diff --git a/docs/document/content/overview/mode.cn.md b/docs/document/content/overview/mode.cn.md index 581550e3bd1..4602542d146 100644 --- a/docs/document/content/overview/mode.cn.md +++ b/docs/document/content/overview/mode.cn.md @@ -5,16 +5,12 @@ weight = 5 chapter = true +++ -Apache ShardingSphere 是一套完善的产品,使用场景非常广泛。 除生产环境的集群部署之外,还为工程师在开发和自动化测试等场景提供相应的运行模式。 Apache ShardingSphere 提供的 3 种运行模式分别是内存模式、单机模式和集群模式。 +Apache ShardingSphere 是一套完善的产品,使用场景非常广泛。 除生产环境的集群部署之外,还为工程师在开发和自动化测试等场景提供相应的运行模式。 Apache ShardingSphere 提供的 2 种运行模式分别是单机模式和集群模式。 -### 内存模式 - -初始化配置或执行 SQL 等造成的元数据结果变更的操作,仅在当前进程中生效。 适用于集成测试的环境启动,方便开发人员在整合功能测试中集成 Apache ShardingSphere 而无需清理运行痕迹。 - -### 单机模式 +## 单机模式 能够将数据源和规则等元数据信息持久化,但无法将元数据同步至多个 Apache ShardingSphere 实例,无法在集群环境中相互感知。 通过某一实例更新元数据之后,会导致其他实例由于获取不到最新的元数据而产生不一致的错误。 适用于工程师在本地搭建 Apache ShardingSphere 环境。 -### 集群模式 +## 集群模式 提供了多个 Apache ShardingSphere 实例之间的元数据共享和分布式场景下状态协调的能力。 在真实部署上线的生产环境,必须使用集群模式。它能够提供计算能力水平扩展和高可用等分布式系统必备的能力。 集群环境需要通过独立部署的注册中心来存储元数据和协调节点状态。 diff --git a/docs/document/content/overview/mode.en.md b/docs/document/content/overview/mode.en.md index c0b66e451c1..0ceb082e7ad 100644 --- a/docs/document/content/overview/mode.en.md +++ b/docs/document/content/overview/mode.en.md @@ -5,17 +5,13 @@ weight = 5 chapter = true +++ -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 three operation modes: memory mode, standalone mode, and cluster mode. +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 operation modes: standalone mode and cluster mode. -### Memory mode - -Initial configuration or metadata changes caused by SQL execution take effect only in the current process. Suitable for environment setup of integration testing, it makes it easy for developers to integrate Apache ShardingSphere in integrated functional testing without cleaning the running traces. This is the default mode of Apache ShardingSphere. - -### Standalone 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. 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 +## 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. diff --git a/docs/document/static/img/overview.cn_v2.png b/docs/document/static/img/overview.cn_v2.png index 2dc394d587d..f98ab199dc7 100644 Binary files a/docs/document/static/img/overview.cn_v2.png and b/docs/document/static/img/overview.cn_v2.png differ diff --git a/docs/document/static/img/overview.en.png b/docs/document/static/img/overview.en.png index 9233670de9f..9a19ab41ff4 100644 Binary files a/docs/document/static/img/overview.en.png and b/docs/document/static/img/overview.en.png differ