. . . . . . . . . . . . . . . 5 2.3.1 L1 Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3.2 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3.3 L3 Ecosystem Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3 Deployment 7 3.1 Using ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . ecosystem around the upper layer of the platform. Database Plus, the design phi‐ losophy of Apache ShardingSphere, aims at building the standard and ecosystem on the upper layer of the heterogeneous database

. . . . . . . . . . . . . . . 5 2.3.1 L1 Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3.2 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3.3 L3 Ecosystem Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3 Deployment 7 3.1 Using ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . ecosystem around the upper layer of the platform. Database Plus, the design phi‐ losophy of Apache ShardingSphere, aims at building the standard and ecosystem on the upper layer of the heterogeneous database

Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 L3 Ecosystem Layer . . . ecosystem around the upper layer of the platform. Database Plus, the design phi‐ losophy of Apache ShardingSphere, aims at building the standard and ecosystem on the upper layer of the heterogeneous database ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. ShardingSphere-Proxy ShardingSphere‐Proxy is a transparent database proxy, providing a database

Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 L3 Ecosystem Layer . . . ecosystem around the upper layer of the platform. Database Plus, the design phi‐ losophy of Apache ShardingSphere, aims at building the standard and ecosystem on the upper layer of the heterogeneous database ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. 1 Apache ShardingSphere document, v5.2.0 ShardingSphere-Proxy ShardingSphere‐Proxy is a transparent

Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 L3 Ecosystem Layer . . multi‐model databases. It focuses on how to reuse existing databases and their re‐ spective upper layer, rather than creating a new database. The concepts at the core of the project are Link, Enhance and ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to the database, it provides services in the form of a jar

Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 L3 Ecosystem Layer . . Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to the database, it provides services in the form of a jar

Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 L2 Feature Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 L3 Ecosystem Layer . . Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to the database, it provides services in the form of a jar

ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end connecting directly to the database, it provides service in the form of jar vironment, in charge of all the access to the database in the form of sidecar. It provides a mesh layer interacting with the database, we call this as Database Mesh. Database Mesh emphasizes on how to they just need to be put into the right position accordingly. They are all gov‐ erned by the mesh layer. 1.1. Introduction 2 Apache ShardingSphere document, v5.0.0-beta Shardi ngSphere-JDBC Shardin gSphere-Proxy

命名只允许使用字母、数字以及 _ ，且必须以字母开头； • poolProperty 用于自定义连接池参数，key 必须和连接池参数名一致； • ifNotExists 子句用于避免出现 Duplicate storage unit 的错误。 示例 • 使用标准模式注册存储单元 REGISTER STORAGE UNIT ds_0 ( HOST="127.0.0.1", PORT=3306 策略可参考分布式 主键； • AUDIT_STRATEGY 用于指定分配审计生成策略，为可选项，关于分片审计生成策略可参考分片审 计； • ifNotExists 子句用于避免出现 Duplicate sharding rule 错误。 示例 1. 标准分片规则 CREATE SHARDING TABLE RULE t_order_item ( DATANODES("ds_${0. SHARDING_COLUMNS 指定多个分片键； • algorithmType 为分片算法类型，详细的分片算法类型信息请参考分片算法； • ifNotExists 子句用于避免出现 Duplicate default sharding strategy 错误。 示例 • 创建默认分表策略 CREATE DEFAULT SHARDING TABLE STRATEGY ( TYPE="standard"

命名只允许使用字母、数字以及 _ ，且必须以字母开头； • poolProperty 用于自定义连接池参数，key 必须和连接池参数名一致； • ifNotExists 子句用于避免出现 Duplicate storage unit 的错误。 示例 • 使用标准模式注册存储单元 REGISTER STORAGE UNIT ds_0 ( HOST="127.0.0.1", PORT=3306 策略可参考分布式 主键； • AUDIT_STRATEGY 用于指定分配审计生成策略，为可选项，关于分片审计生成策略可参考分片审 计； • ifNotExists 子句用于避免出现 Duplicate sharding rule 错误。 示例 1. 标准分片规则 CREATE SHARDING TABLE RULE t_order_item ( DATANODES("ds_${0. SHARDING_COLUMNS 指定多个分片键； • algorithmType 为分片算法类型，详细的分片算法类型信息请参考分片算法； • ifNotExists 子句用于避免出现 Duplicate default sharding strategy 错误。 示例 • 创建默认分表策略 CREATE DEFAULT SHARDING TABLE STRATEGY ( TYPE="standard"