transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction transaction and high concurrency situation of the Internet. With a high access cost, soft transactions require developers to transform the application and realize resources lock and backward compensa‐ tion. the database chosen by yourself. Usage Sharding with Hint Hint Configuration Hint algorithms require users to implement the interface of org.apache.shardingsphere.api. sharding.hint.HintShardingAlgorithm

transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction transaction and high concurrency situation of the Internet. With a high access cost, soft transactions require developers to transform the application and realize resources lock and backward compensa‐ tion. the database chosen by yourself. Usage Sharding with Hint Hint Configuration Hint algorithms require users to implement the interface of org.apache.shardingsphere.api. sharding.hint.HintShardingAlgorithm

database sources. It is suitable for scenarios where the amount of data is not large and does not require any sharding operations. Sharding Sharding Key The database field used in sharding refers to the in sharding settings into actual table names acquired after routing. Database sharding does not require to rewrite table names. In addition to that, there are also column derivation, pagination information corresponding data. Merging result set by moving down its cursor is called stream merger. It does not require to load all the query results to the memory. Thus, it is able to save memory resource effectively

transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction transaction and high concurrency situation of the Internet. With a high access cost, soft transactions require developers to transform the application and realize resources lock and backward compensa‐ tion. unified coordination and the synchronization of policies and rules between different nodes also require us to design a set of global event notification mechanisms and distributed coordination lock mechanisms

Primary Key In traditional database software development, automatic primary key generation is a basic require‐ ment. Various databases provide support for this requirement, such as self‐incrementing keys of transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction access cost, soft transactions 8.2. Distributed Transaction 33 Apache ShardingSphere document require developers to transform the application and realize resources lock and backward compensa‐ tion.

Primary Key In traditional database software development, automatic primary key generation is a basic require‐ ment. Various databases provide support for this requirement, such as self‐incrementing keys of transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction access cost, soft transactions 8.2. Distributed Transaction 33 Apache ShardingSphere document require developers to transform the application and realize resources lock and backward compensa‐ tion.

Primary Key In traditional database software development, automatic primary key generation is a basic require‐ ment. Various databases provide support for this requirement, such as self‐incrementing keys of transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction transaction and high concurrency situation of the Internet. With a high access cost, soft transactions require developers to transform the application and realize resources lock and backward compensa‐ tion.

Primary Key In traditional database software development, automatic primary key generation is a basic require‐ ment. Various databases provide support for this requirement, such as self‐incrementing keys of transactions. But in distributed application situations based on micro‐services, more and more of them require to include multiple accesses to services and the corresponding database resources in the same transaction transaction and high concurrency situation of the Internet. With a high access cost, soft transactions require developers to transform the application and realize resources lock and backward compensa‐ tion.

algorithm class name used for `=` and `IN`. This class need to implements PreciseShardingAlgorithm, and require a no argument constructor sharding.jdbc.config.sharding.tables..database-strategy algorithm class name used for `BETWEEN`. This class need to implements RangeShardingAlgorithm, and require a no argument constructor #Complex sharding scenario for multiple sharding columns sharding.jdbc sharding algorithm class name. This class need to implements ComplexKeysShardingAlgorithm, and require a no argument constructor #Inline expression sharding scenario for si-gle s-arding column sharding

Development ElasticJob has two kinds of job types: Class‐based job and Type‐based job. Class‐based jobs require developers to weave business logic by implementing interfaces; Type‐based jobs don’t need coding