database connection pool, such as DBCP, C3P0, BoneCP, Druid, HikariCP. • Supports any kind of JDBC standard database: MySQL, Oracle, SQLServer, PostgreSQL and any SQL92 followed databases. 1.1. Introduction database connection pool, such as DBCP, C3P0, BoneCP, Druid, HikariCP. • Support any kind of JDBC standard database: MySQL, Oracle, SQLServer, PostgreSQL and any SQL92 followed databases. 10 Apache ShardingSphere DistSQL（Distributed SQL）is Apache ShardingSphere specific SQL, which provide added‐on operation capability beside standard SQL. 3.3.2 Challenges When using ShardingSphere‐Proxy, developers can operate data just like using

database connection pool, such as DBCP, C3P0, BoneCP, Druid, HikariCP. • Support any kind of JDBC standard database: MySQL, Oracle, SQLServer, PostgreSQL and any SQL92 followed databases. 1.1.2 ShardingSphere-Proxy data in one database and storing them in multiple tables and databases according to some certain standard, so that the performance and availability can be improved. Both 8 Apache ShardingSphere document processing volume in single ma‐ chine and can be extended relatively freely, so it can be taken as a standard solution to database sharding and table sharding. 3.1.2 Challenges Though sharding has solved

Contributors Over Time Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases third‐party database connection pool, such as DBCP, C3P0, BoneCP, HikariCP; • Support any kind of JDBC standard database: MySQL, PostgreSQL, Oracle, SQLServer and any JDBC adapted databases. 1.1.2 ShardingSphere-Proxy third‐party database connection pool, such as DBCP, C3P0, BoneCP, HikariCP; • Support any kind of JDBC standard database: MySQL, PostgreSQL, Oracle, SQLServer and any JDBC adapted databases. 10 Apache ShardingSphere

Contributors Over Time Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases third‐party database connection pool, such as DBCP, C3P0, BoneCP, HikariCP; • Support any kind of JDBC standard database: MySQL, PostgreSQL, Oracle, SQLServer and any JDBC adapted databases. 1.1.2 ShardingSphere-Proxy third‐party database connection pool, such as DBCP, C3P0, BoneCP, HikariCP; • Support any kind of JDBC standard database: MySQL, PostgreSQL, Oracle, SQLServer and any JDBC adapted databases. 10 Apache ShardingSphere

. . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2.1 Connect: Create database upper level standard . . . . . . . . . . . . . . . . . . 4 1.2.2 Enhance: Database computing enhancement engine . . 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. It focuses on how to make full Philosophy 3 Apache ShardingSphere document, v5.2.1 1.2.1 Connect: Create database upper level standard Through flexible adaptation of database protocols, SQL dialects, and database storage, it can quickly

. . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.1 Connect: Create database upper level standard . . . . . . . . . . . . . . . . . . 5 1.2.2 Enhance: Database computing enhancement engine . . 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. It focuses on how to make full Philosophy 4 Apache ShardingSphere document, v5.2.0 1.2.1 Connect: Create database upper level standard Through flexible adaptation of database protocols, SQL dialects, and database storage, it can quickly

. . . . . . . . . . . . . . 2 2 Design Philosophy 4 2.1 Connect: Create database upper level standard . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Enhance: Database computing enhancement engine 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. It focuses on how to make full database in the ecology. 4 Apache ShardingSphere document 2.1 Connect: Create database upper level standard Through flexible adaptation of database protocols, SQL dialects, and database storage, it can quickly

. . . . . . . . . . . . . . 2 2 Design Philosophy 4 2.1 Connect: Create database upper level standard . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Enhance: Database computing enhancement engine 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. It focuses on how to make full database in the ecology. 4 Apache ShardingSphere document 2.1 Connect: Create database upper level standard Through flexible adaptation of database protocols, SQL dialects, and database storage, it can quickly

provider Implementation Class Description Defau ltJobClassNameProvider Job class name provider in standard environment SpringPro xyJobClassNameProvider Job class name provider in Spring container environment required Mesos native library. Specify Mesos native library path by property -Djava. library.path. For instance, Mesos native libraries are under /usr/local/lib, so the property -Djava.library. path=/usr/local/lib

t_order${0..1} # 配置分库策略 databaseStrategy: standard: shardingColumn: user_id shardingAlgorithmName: database_inline # 配置分表策略 tableStrategy: standard: shardingColumn: order_id shardingAlgorithmName: rules.sharding.tables.t_order.database-strategy.standard. sharding-column=user_id spring.shardingsphere.rules.sharding.tables.t_order.database-strategy.standard. sharding-algorithm-name=database_inline rules.sharding.tables.t_order.table-strategy.standard. sharding-column=order_id spring.shardingsphere.rules.sharding.tables.t_order.table-strategy.standard. sharding-algorithm-name=table_inline # 省略配置