distributed scenarios which provides metadata sharing and state coordination among multiple computing nodes. It is necessary to provide registry center for distributed coordination, such as ZooKeeper or Etcd syntactic sugar for sharding algorithm. It used to manage all data nodes automatically, user do not care about the topology of physical data nodes. It includes lots of implementation for Mod, Hash, Range and related to business imple‐ mentation, and allows users to manage the physical topology physical data nodes by themselves. It includes: • Standard Sharding Algorithm It is to process the sharding case in

Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Sharding . . . . 45 8.6.6 Core Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Cluster . . data_sources/units/ds_0/versions/0 . . . . . . . . . 495 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 495 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0

Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Sharding . . . . 45 8.6.6 Core Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Cluster . . data_sources/units/ds_0/versions/0 . . . . . . . . . 524 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 524 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0

main problems that inline expression intends to solve. In complex sharding rules, with more data nodes, a large number of configuration repetitions make configurations difficult to maintain. Inline expressions $->{ expression } to identify them. ShardingSphere currently supports the configurations of data nodes and sharding algorithms. Inline expressions use Groovy syntax, which can support all kinds of operations offline_table1, offline_table2, offline_table3 Data Node Configuration For evenly distributed data nodes, if the data structure is as follow: db0 ├── t_order0 └── t_order1 db1 ├── t_order0 └── t_order1

data_sources/units/ds_0/versions/0 . . . . . . . . . 438 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 438 ix /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 emaName}/tables/t_order/versions/0 . . 439 /nodes/compute_nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 /nodes/storage_nodes . . . . . . . . . . . . . . . . . . . . . . . ZooKeeper helm chart ## enabled: true ## @param governance.zookeeper.replicaCount Number of ZooKeeper nodes ## replicaCount: 1 ## ZooKeeper Persistence parameters ## ref: https://kubernetes.io/docs/use

data_sources/units/ds_0/versions/0 . . . . . . . . . 459 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 459 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 emaName}/tables/t_order/versions/0 . . 460 /nodes/compute_nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 /nodes/storage_nodes . . . . . . . . . . . . . . . . . . . . . . . ZooKeeper helm chart ## enabled: true ## @param governance.zookeeper.replicaCount Number of ZooKeeper nodes ## replicaCount: 1 ## ZooKeeper Persistence parameters ## ref: https://kubernetes.io/docs/use

data_sources/units/ds_0/versions/0 . . . . . . . . . 485 /metadata/${databaseName}/data_sources/nodes/ds_0/versions/0 . . . . . . . . . 485 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 as/{schemaName}/tables/t_order/versions/0 . . 486 /nodes/compute_nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 /nodes/qualified_data_sources . . . . . . . . . . . . . . . ZooKeeper helm chart ## enabled: true ## @param governance.zookeeper.replicaCount Number of ZooKeeper nodes ## replicaCount: 1 ## ZooKeeper Persistence parameters ## ref: https://kubernetes.io/docs/use

├ ├ ├──dataSources # 数据源配置 ├ ├ ├──rules # 规则配置 ├ ├ ├──schema # 表结构配置 ├──status ├ ├──compute_nodes ├ ├ ├──online ├ ├ ├ ├──${your_instance_ip_a}@${your_instance_port_x} ├ ├ ├ ├──${your_instance_ nce_port_v} ├ ├ ├ ├──${your_instance_ip_d}@${your_instance_port_w} ├ ├ ├ ├──.... ├ ├──storage_nodes ├ ├ ├──disable ├ ├ ├ ├──${schema_1.ds_0} ├ ├ ├ ├──${schema_1.ds_1} ├ ├ ├ ├──.... ├ ├ ├──primary caseSensitive: false dataType: 0 generated: false name: order_id primaryKey: false /status/compute_nodes 数据库访问对象运行实例信息，子节点是当前运行实例的标识。运行实例标识由运行服务器的 IP 地址和 PORT 构成。运行实例标识均为临时节点，当实例上线时注册，下线时自动清理。注册中心监控这些节点

. . . . . . . . . . . . . . . . . . . 254 /nodes/compute_nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 /nodes/storage_nodes . . . . . . . . . . . . . . . . . . . . . . . distributed scenarios which provides metadata sharing and state coordination among multiple computing nodes. It is necessary to provide registry center for distributed coordination, such as ZooKeeper or Etcd failure. Centralized management is to uniformly manage the state of database storage nodes and middleware computing nodes, and can detect the latest updates in the distributed environment in real time, further

. . . . . . . . . . . . . . . . . . . 243 /nodes/compute_nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 /nodes/storage_nodes . . . . . . . . . . . . . . . . . . . . . . . distributed scenarios which provides metadata sharing and state coordination among multiple computing nodes. It is necessary to provide registry center for distributed coordination, such as ZooKeeper or Etcd failure. Centralized management is to uniformly manage the state of database storage nodes and middleware computing nodes, and can detect the latest updates in the distributed environment in real time, further