set of distributed database solu‐ tions, including 3 independent products, JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale out, distributed transaction and distributed governance Transaction 66 Apache ShardingSphere document, v5.0.0-beta Unsupported Items • Recover committing and rolling back in other machines after the service is down. Seata BASE transaction Supported Items • Support Language）responsible for the added‐on feature of hint, transaction type switch, sharding execute planning and so on. 3.8.3 Goal It is the design goal of DistSQL to break the boundary between middleware

1.1 Introduction Apache ShardingSphere including 3 independent products: JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale‐out, distributed transaction and distributed governance responsible for the added‐on administrator fea‐ ture of hint, transaction type switch, sharding execute planning and so on. 3.3. DistSQL 14 Apache ShardingSphere document, v5.0.0 3.3.3 Goal It is the design Distributed Transaction 44 Apache ShardingSphere document, v5.0.0 Unsupported • Recover committing and rolling back in other machines after the service is down. BASE Supported • Support cross‐database transactions

1.1 Introduction Apache ShardingSphere including 3 independent products: JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale‐out, distributed transaction and distributed governance responsible for the added‐on administrator fea‐ ture of hint, transaction type switch, sharding execute planning and so on. 3.3. DistSQL 14 Apache ShardingSphere document, v5.1.2 3.3.3 Goal It is the design Distributed Transaction 49 Apache ShardingSphere document, v5.1.2 Unsupported • Recover committing and rolling back in other machines after the service is down; • MySQL,in the transaction block, the SQL execution

1.1 Introduction Apache ShardingSphere including 3 independent products: JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale‐out, distributed transaction and distributed governance responsible for the added‐on administrator fea‐ ture of hint, transaction type switch, sharding execute planning and so on. 3.3. DistSQL 14 Apache ShardingSphere document, v5.1.1 3.3.3 Goal It is the design Distributed Transaction 47 Apache ShardingSphere document, v5.1.1 Unsupported • Recover committing and rolling back in other machines after the service is down. • Savepoint. • In the transaction block, the

Distributed Transaction 33 Apache ShardingSphere document, v5.2.0 Unsupported • Recover committing and rolling back in other machines after the service is down; • MySQL,in the transaction block, the SQL execution object configured as Spring bean can be used with the Spring namespace of ShardingSphere‐JDBC Data Planning. The database driver in the example is MySQL and the connection pool is HikariCP, both of which middle layer of the database, and distributed databases can achieve elastic scalability. In the planning of ShardingSphere, the elastic scaling function will be available at V4.x. Sharding Route The

Distributed Transaction 32 Apache ShardingSphere document, v5.2.1 Unsupported • Recover committing and rolling back in other machines after the service is down; • MySQL,in the transaction block, the SQL execution object configured as Spring bean can be used with the Spring namespace of ShardingSphere‐JDBC Data Planning. The database driver in the example is MySQL and the connection pool is HikariCP, both of which middle layer of the database, and distributed databases can achieve elastic scalability. In the planning of ShardingSphere, the elastic scaling function will be available at V4.x. Sharding Route The

During the zk authorization upgrade process, there was a false death of the instance during the rolling deployment process, and even if the historical version was rolled back, there was still false death death of the instance during the rolling deployment process, and even if the historical version was rolled back, there was still false death. Answer: During the rolling deployment process, competitive During the zk authorization upgrade process, there was a false death of the instance during the rolling deployment process, and even if the historical version was rolled back, there was still false death

Transaction 37 Apache ShardingSphere document XA Transaction Unsupported • Recover committing and rolling back in other machines after the service is down. • MySQL, in the transaction block, the SQL execution middle layer of the database, and distributed databases can achieve elastic scalability. In the planning of ShardingSphere, the elastic scaling function will be available at V4.x. Sharding Route The

Transaction 37 Apache ShardingSphere document XA Transaction Unsupported • Recover committing and rolling back in other machines after the service is down. • MySQL, in the transaction block, the SQL execution middle layer of the database, and distributed databases can achieve elastic scalability. In the planning of ShardingSphere, the elastic scaling function will be available at V4.x. Sharding Route The

数据分片 分库 & 分表 读写分离 分布式主键 分布式事务(Doing) XA强一致事务 柔性事务 数据库治理 配置动态化 熔断 & 禁用 调用链路追踪 弹性伸缩 (Planning) 1.7 数据分片工作原理 ShardingSphere的3个产品的数据分片主要流程是完全一致的。 核心由 SQL解析 => 执行器优化 => SQL路由 => SQL改写 =>