distributed database access application with the database. Focusing on interaction, it effectively organizes the interaction between messy applications and the database. The application and database that use high‐performance light‐weight OLTP application developed with Java; ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and unified sharding strategy by the same registry center, ShardingSphere can build an application system applicable to all kinds of scenarios. Architects can adjust the system architecture to

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Mass data high concurrency 3.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 32 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 32 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 32 3.2.6 Related references . . . . . . . . . . . . .

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mass data high concurrency 8.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 36 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 36 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 37 8.2.6 Related references . . . . . . . . . . . . .

high‐performance light‐weight OLTP application developed with Java. ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and a unified sharding strategy by the same registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture High loss Decentralization Yes No Static Entry No Yes ShardingSphere‐JDBC is suitable for java application. 3.1.2 ShardingSphere-Proxy ShardingSphere‐Proxy is the second product of Apache ShardingSphere

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Mass data high concurrency 3.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 31 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 31 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 31 3.2.6 Related references . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 7.1.1 Data Structure in Registry Center . . . . . . . . . . . . . . . . . . . . . . . . . . 240 /rules . . . . . . high‐performance light‐weight OLTP application developed with Java. ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and a unified sharding strategy by the same registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mass data high concurrency 8.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 36 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 36 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 37 8.2.6 Related references . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 7.1.1 Data Structure in Registry Center . . . . . . . . . . . . . . . . . . . . . . . . . . 251 /rules . . . . . . high‐performance light‐weight OLTP application developed with Java. ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and a unified sharding strategy by the same registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture

Distributed Implementation . . . . . . . . . . . . . . . . . . . . . . . . . 10 Registry Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 config node . . . . . . . . Use Spring Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Table Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 6.1.4 Operation API 6.3.1 Deploy Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Application deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Operation and maintenance

SQL databases and objects in Java, .NET, and Ruby on Rails. The mappings are decoupled from the application logic by packaging the SQL statements in XML configuration files. It abstracts almost all of the Interfaces − MyBatis provides database-independent interfaces and APIs that help the rest of the application remain independent of any persistence-related resources. Open source− MyBatis is free and an open the form of stored procedures so that business logic can be kept out of the database, and the application is more portable and easier to deploy and test. Supports inline SQL − No pre-compiler is needed