ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted. Will create a .shardingsphere file in the root directory ShardingSphere document, v5.1.1 Broadcast Table It refers to tables that exist in all sharding database sources. The schema and data must consist in each database. It can be applied to the small data volume that table for example. Single Table It refers to only one table that exists in all sharding database sources. It is suitable for little data in table without sharding. Data Node As the atomic unit of sharding

ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted. Will create a .shardingsphere file in the root directory be totally identical. Broadcast Table It refers to tables that exist in all sharding database sources. The schema and data must consist in each database. It can be applied to the small data volume that table for example. Single Table It refers to only one table that exists in all sharding database sources. It is suitable for little data in table without sharding. Data Node As the atomic unit of sharding

document, v5.0.0-beta Broadcast Table It refers to tables that exist in all sharding database sources. Their structures and data are the same in each database. It can be applied to the small data volume table for example. Single Table It refers to only one table that exists in all sharding database sources. It is suitable for scenarios where the amount of data is not large and does not require any sharding replica query. 3.1. Sharding 14 Apache ShardingSphere document, v5.0.0-beta Data Sources Configuration Real data sources list. Tables Configuration Configurations of logic table names, data node and

ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted. Will create a .shardingsphere file in the root directory conditions of t_order. Broadcast Table It refers to tables that exist in all sharding database sources. The schema and data must consist in each database. It can be applied to the small data volume that table for example. Single Table It refers to only one table that exists in all sharding database sources. It is suitable for little data in table without sharding. Data Node As the atomic unit of sharding

transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Read/write Split‐ ting Read/write splitting can be used to cope with business access with high data sources. Data Mi‐ gra‐ tion Data migration is the key to connecting data ecosystems. SharingSphere provides migra‐ tion capabilities to help users migrate the data from other data sources, while environment. Sharding‐ Sphere provides complex data query and analysis capabilities across data sources, simpli‐ fying the data aggregation from different data locations. Data En‐ cryp‐ tion Data

ca‐ pability on top of a single database, which can achieve data security across underlying data sources. Read/write Split‐ ting Read/write splitting can be used to cope with business access with high data environment. Sharding‐ Sphere is capable of querying and analyzing complex data across data sources, simplifying and improving the data usage experience. Data En‐ cryp‐ tion Data Encryption is 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

. . . . . . . . . 524 /metadata/${databaseName}/data_sources/units/ds_0/versions/0 . . . . . . . . . 524 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 524 /metadata /nodes/compute_nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 /nodes/qualified_data_sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 12.4 Sharding . . . . . . . . . . . transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Re ad /w ri te S pl it ti ng Read/write splitting can be used to cope with business access

省略 # 自动分片表配置 spring.shardingsphere.rules.sharding.auto-tables..actual-data- sources= # 数据源名 spring.shardingsphere.rules.sharding.auto-tables..sharding- strategy.standard rules.readwrite-splitting.data-sources..write-data-source-name= # 写数据源名称 spring.shardingsphere.rules.readwrite-splitting.data-sources. read-data-source-names= # 读数据源名称，多个从数据源用逗号分隔 spring.shardingsphere.rules.readwrite-splitting.data-sources..load-balancer-name= # 负载均衡算法名称 # 负载均衡算法配置 spring.shardingsphere

. . . . . . . . . 495 /metadata/${databaseName}/data_sources/units/ds_0/versions/0 . . . . . . . . . 495 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 495 /metadata transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Re ad /w ri te S pl it ti ng Read/write splitting can be used to cope with business access ShardingSphere provides mi‐ gration capabilities to help users migrate the data from other data sources, while simul‐ taneously performing data sharding. Q ue ry Fe de ra ti on Federated queries are

省略 # 自动分片表配置 spring.shardingsphere.rules.sharding.auto-tables..actual-data- sources= # 数据源名 spring.shardingsphere.rules.sharding.auto-tables..sharding- strategy.standard readwrite-splitting.data-sources..static-strategy.write-data-source-name= # 写库数据源名称 spring.shardingsphere.rules.readwrite-splitting.data-sources.sources..load-balancer-name= # 负载均衡算法名称 # 负载均衡算法配置 spring.shardingsphere