301 viii 1 Overview Stargazers over time Contributor over time Apache ShardingSphere is an open‐source ecosystem consisted of a set of distributed database solu‐ tions, including 3 independent 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

MYBATIS - QUICK GUIDE MYBATIS - QUICK GUIDE MYBATIS - OVERVIEW MYBATIS - OVERVIEW MyBatis is an open source, lightweight, persistence framework. It is an alternative to JDBC and Hibernate. It automates 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 and APIs that help the rest of the application remain independent of any persistence-related resources. Open source− MyBatis is free and an open source software. Advantages of MYBATIS MYBATIS

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 . . . . . . . . . . . . .

is positioned as a Database Plus, and aims at building a new criterion and ecosystem above multi‐model databases. It focuses on how to reuse existing databases and their re‐ spective upper layer, rather 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‐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 Notice: Please change ${latest.release.version} to the actual version. 3. Edit application.yml. spring: shardingsphere: datasource: names: ds_0, ds_1 ds_0: type: com.zaxxer.hikari

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 . . . . . . . . . . . . .

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5 Concepts & Features 7 5.1 Schedule Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2 Elastic Schedule Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.5 Job Open Ecosystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.5.1 Job 6.3.1 Deploy Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Application deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Operation and maintenance

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 . . . . . . . . . . . . .

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 . . . . . . . . . . . . .