. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4 Running Modes 11 4.1 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2 Cluster . . . . . . . . . . . . 546 13.1.1 MODE What is the difference between standalone mode Standalone and Com- patible_Standalone? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 13.1.2 and BASE transac‐ tions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Re ad /w ri te S pl it ti

1.3.2 Running Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Cluster mode . v5.2.0 1.3.2 Running Modes 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 2.5 Application Scenarios The database’s transactions can meet ACID business requirements in a standalone application scenario. However, in distributed scenarios, traditional database solutions cannot

Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.1 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.2 Cluster Mode and BASE trans‐ actions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Read/write Split‐ ting Read/write 2.1 1.4 Running Modes Apache ShardingSphere provides two running modes: standalone mode and cluster mode. 1.4.1 Standalone Mode It can achieve data persistence in terms of metadata information such

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4 Running Modes 11 4.1 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2 Cluster and BASE transac‐ tions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Re ad /w ri te S pl it ti Architecture 10 4 Running Modes Apache ShardingSphere provides two running modes: standalone mode and cluster mode. 4.1 Standalone Mode It can achieve data persistence in terms of metadata information such

2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.4 Cluster mode integration function testing. This is the default mode of Apache ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted use cost. Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database

2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.4 Cluster mode integration function testing. This is the default mode of Apache ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted use cost. Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database

2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 i 3.2.4 Cluster mode integration function testing. This is the default mode of Apache ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted use cost. Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database

可配置属性： 名称 数据类型 说明 type (?) String Memory Standalone 模式 配置入口 类名称：org.apache.shardingsphere.infra.config.mode.ModeConfiguration 名称 数据类型 说明 type String Standalone reposi‐ tory PersistReposito ryConfigu‐ mode.repository.standalone.StandalonePersistRepositoryConfiguration 可配置属性： 名称 数据类型 说明 type String Standalone 配置持久化类型。如：File props (?) Properties Standalone 配置持久化的属性如：path 路径 Standalone 属性配置： 名称 数据类型 type: # Memory Standalone mode schema: name: # JDBC 数据源别名。可选项，不配置则默认采用 logic_db 作为 schemaName，该参数可实现 JDBC 与 PROXY 共享配置 mode: type: # Standalone repository: type: # Standalone 配置持久化类型。如：File props:

参数解释 mode (?): # 不配置则默认单机模式 type: # 运行模式类型。可选配置：Standalone、Cluster repository (?): # 久化仓库配置 overwrite: # 是否使用本地配置覆盖持久化配置 单机模式 mode: type: Standalone repository: type: # 持久化仓库类型 props: # 持久化仓库所需属性 是否使用本地配置覆盖持久化配置 注意事项 1. 生产环境建议使用集群模式部署。 2. 集群模式部署推荐使用 ZooKeeper 注册中心。 配置示例 单机模式 mode: type: Standalone repository: type: File overwrite: false 集群模式 (推荐) mode: type: Cluster repository: type: ShardingSphere-JDBC 77 Apache ShardingSphere document, v5.2.0 Standalone 持久化配置 类名称：org.apache.shardingsphere.mode.repository.standalone.StandalonePersistRepositoryConfiguration 可配置属性： 名称 数据类型 说明 type

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 13.1.1 MODE 单机模式 Standalone 和 Compatible_Standalone 区别? . . . . . . 505 13.1.2 MODE 集群模式 Cluster 和 Compatible_Cluster 区别? . . . . . . 表示数组，可以与减号相互替换使用 模式配置 参数解释 mode (?): # 不配置则默认单机模式 type: # 运行模式类型。可选配置：Standalone、Cluster repository (?): # 持久化仓库配置 单机模式 mode: type: Standalone repository: type: # 持久化仓库类型 props: # 持久化仓库所需属性 foo_key: foo_value 集群模式部署推荐使用 ZooKeeper 注册中心。 3. ZooKeeper 存在配置信息时，则以 ZooKeeper 中的配置为准。 配置示例 单机模式 mode: type: Standalone repository: type: JDBC 集群模式 (推荐) mode: type: Cluster repository: type: ZooKeeper props: