2.3.4 4. Create Migration Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3 Concepts & Features 8 3.1 Sharding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Manual for more details. 2.3. ShardingSphere-Scaling(Alpha) 7 3 Concepts & Features This chapter describes concepts and features about Apache ShardingSphere. Please refer to User man‐ ual for Concept Overview This chapter is to introduce core concepts of data sharding, including: • Core concepts of SQL • Core concepts of sharding • Core concepts of configuration • Inline expression • Distributed

2.3.5 5. Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 Concepts 10 3.1 Adaptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Pluggable. • Link: Flexible adaptation of database Manual#Scaling : SPI interfaces and implementations 2.3. ShardingSphere-Scaling (Experimental) 9 3 Concepts The functions of Apache ShardingSphere are pretty complex with hundreds of modules, but the con‐

2.3.5 Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 Concepts 10 3.1 Adaptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . goal is to minimize or eliminate the challenges caused by underlying databases fragmentation. The concepts at the core of the project are Connect, Enhance and Pluggable. • Connect: Flexible adaptation of Manual#Scaling : SPI interfaces and implementations 2.3. ShardingSphere-Scaling (Experimental) 9 3 Concepts The functions of Apache ShardingSphere are pretty complex with hundreds of modules, but the con‐

Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Related Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Impact on the System transaction adopts the concepts including AP(application program), YM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted compute: ## @section Compute-Node ShardingSphere-Proxy parameters ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param

Schedule Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5 Concepts & Features 7 5.1 Schedule Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . () { // create job configuration // ... } } 4.3. Configure Job 6 5 Concepts & Features This chapter describes concepts and features about ElasticJob. Please refer to User manual for more details

Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Related Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Impact on the System transaction adopts the concepts including AP(application program), TM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted compute: ## @section Compute-Node ShardingSphere-Proxy parameters ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param

9 2.2.5 Use ShardingSphere‐Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 Concepts 10 3.1 Adaptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . goal is to minimize or eliminate the challenges caused by underlying databases fragmentation. The concepts at the core of the project are Connect, Enhance and Pluggable. • Connect: Flexible adaptation of -u${proxy_username} -p${proxy_password} -h${proxy_host} -P${proxy_port} 2.2. ShardingSphere-Proxy 9 3 Concepts The functions of Apache ShardingSphere are pretty complex with hundreds of modules, but the con‐

Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Related Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Impact on the System transaction adopts the concepts including AP(application program), TM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted compute: ## @section Compute-Node ShardingSphere-Proxy parameters ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param

Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Related Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Impact on the System transaction adopts the concepts including AP(application program), TM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted compute: ## @section Compute-Node ShardingSphere-Proxy parameters ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param

ShardingSphere-Proxy 175 Apache ShardingSphere document, v5.2.0 ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param imagePullSecrets: [] ## ShardingSphere-Proxy resource requests and limits ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources- containers/ ## @param compute.resources.limits The resources limits Deployment Configuration ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/ ## ref: https://kubernetes.io/docs/concepts/services-networking/service/ ## @param compute.replicas