2 Distributed Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.3 Database Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2 Quick Start 5 2 . . . . . . . . . . . . . . . . . . . 68 Primary Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Replica Database . . . . . . . . . . . . . . . . . . . . . . . . . return result of inline expression? . . . . . . . . . 294 7.6 If sharding database is partial, should tables without sharding database & table be con‐ figured in sharding rules? . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . 47 Primary Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Replica Database . . . . . . . . . . . . . . . . . . . . . . . . . Use Norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Shadow database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Shadow algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.7.6 6. [Proxy] How to use a suitable database tools connecting ShardingSphere‐Proxy?305 7.7.7 7. [Proxy] When using a client such as Navicat

. . . . . . . . . . . . . . . . . . . 53 Primary Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Replica Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Production Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Shadow Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 7.8.6 [Proxy] How to use a suitable database tools connecting ShardingSphere‐Proxy? 347 7.8.7 [Proxy] When using a client such as Navicat to

. . . . . . . . . . . . . . . . . . . 55 Primary Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Replica Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Production Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Shadow Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 7.8.6 [Proxy] How to use a suitable database tools connecting ShardingSphere‐Proxy? 359 7.8.7 [Proxy] When using a client such as Navicat to

Create database upper level standard . . . . . . . . . . . . . . . . . . 5 1.2.2 Enhance: Database computing enhancement engine . . . . . . . . . . . . . . . 5 1.2.3 Pluggable: Building database function Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Complex primary‐secondary database architecture . . . . . . . . . . . . . . . . . 36 3.3.5 Related References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Primary database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Secondary database . . . . . . . . . . . . . . . . . . . . . . . . .

Create database upper level standard . . . . . . . . . . . . . . . . . . 4 1.2.2 Enhance: Database computing enhancement engine . . . . . . . . . . . . . . . 4 1.2.3 Pluggable: Building database function Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Complex primary‐secondary database architecture . . . . . . . . . . . . . . . . . 35 3.3.5 Related References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Primary database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Secondary database . . . . . . . . . . . . . . . . . . . . . . . . .

. . 2 2 Design Philosophy 4 2.1 Connect: Create database upper level standard . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Enhance: Database computing enhancement engine . . . . . . . . . . . . . . . . . . . 5 2.3 Pluggable: Building database function ecology . . . . . . . . . . . . . . . . . . . . . . . 5 2.3.1 L1 Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Complex primary‐secondary database architecture . . . . . . . . . . . . . . . . . 40 8.3.5 Related References . . . . . . . . . .

. . 2 2 Design Philosophy 4 2.1 Connect: Create database upper level standard . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Enhance: Database computing enhancement engine . . . . . . . . . . . . . . . . . . . 5 2.3 Pluggable: Building database function ecology . . . . . . . . . . . . . . . . . . . . . . . 5 2.3.1 L1 Kernel Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Complex primary‐secondary database architecture . . . . . . . . . . . . . . . . . 40 8.3.5 Related References . . . . . . . . . .

availability in distributed system – Scale out for throughput and efficiency improvement – Job processing capacity is flexible and scalable with the allocation of resources • Resource Assign – Execute Elastic Schedule Elastic schedule is the most important feature in ElasticJob, which acts as a job processing system that enables the horizontal scaling of jobs by sharding, it’s also the origin of the project horizontally split the databases according to the regions, database A stores data from Beijing, database B stores data from Shanghai and database C stores data from Guangzhou. If we config‐ ure only by

of parameters manually and retrieving the results. It provides a simple API to interact with the database. It also provides support for custom SQL, stored procedures and advanced mappings. It was formerly platform such as Java, Ruby, and C# for Microsoft .NET. Independent Interfaces − MyBatis provides database-independent interfaces and APIs that help the rest of the application remain independent of any encapsulates SQL in 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