. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 v Background Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Build GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 147 Use Helm . . . . . . . . . . . . . transactions cannot be avoided, some businesses might still be in the need to maintain transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Background Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Build GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 166 Use Helm . . . . . . . . . . . . . transactions cannot be avoided, some businesses might still be in the need to maintain transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Build GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 185 Use Helm . . . . . . . . . . . . . transactions cannot be avoided, some businesses might still be in the need to maintain transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because in scenarios with high concurrency, and most of them use flexible transactions with ultimate consistency instead of strong consistent transactions. 3.1.3 Goal The main design goal of the data sharding

transactions cannot be avoided, some businesses might still be in the need to maintain transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because in scenarios with high concurrency, and most of them use flexible transactions with ultimate consistency instead of strong consistent transactions. 3.1.3 Goal The main design goal of the data sharding features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity: transactions are executed as a whole, and either all or none is executed. • Consistency: transactions should ensure

Transaction 4.4.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction is treated as a single fails completely; 4.4. Distributed Transaction 44 Apache ShardingSphere document, v5.1.2 • Consistency ensures that a transaction can only bring the database from one valid state to another, maintaining any consumption in performance, local transactions are not capable enough in high consistency and eventual consistency. 2PC Transaction The earliest distributed transaction model of XA standard is X/Open

Transaction 4.4.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction is treated as a single fails completely; 4.4. Distributed Transaction 43 Apache ShardingSphere document, v5.1.1 • Consistency ensures that a transaction can only bring the database from one valid state to another, maintaining any consumption in performance, local transactions are not capable enough in high consistency and eventual consistency. 2PC Transaction The earliest distributed transaction model of XA standard is X/Open

Docker Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Pull Official Docker Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Build Docker Image Manually (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction is treated as a single unit, which either succeeds com‐ pletely, or fails completely; • Consistency ensures any consumption in performance, local transactions are not capable enough in high consistency and eventual consistency. 2PC Transaction The earliest distributed transaction model of XA standard is X/Open

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 背景信息 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 构建 GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 133 使用 Helm . . . . . . . . . . . . . . 2.1 背景 数据库事务需要满足 ACID（原子性、一致性、隔离性、持久性）四个特性。 • 原子性（Atomicity）指事务作为整体来执行，要么全部执行，要么全不执行； • 一致性（Consistency）指事务应确保数据从一个一致的状态转变为另一个一致的状态； • 隔离性（Isolation）指多个事务并发执行时，一个事务的执行不应影响其他事务的执行； • 持久性（Durability）指已提交的事务修改数据会被持久保存。

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 构建 GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 126 可观察性 . . . . . . . . . . . . . . . 2.1 背景 数据库事务需要满足 ACID（原子性、一致性、隔离性、持久性）四个特性。 • 原子性（Atomicity）指事务作为整体来执行，要么全部执行，要么全不执行； • 一致性（Consistency）指事务应确保数据从一个一致的状态转变为另一个一致的状态； • 隔离性（Isolation）指多个事务并发执行时，一个事务的执行不应影响其他事务的执行； • 持久性（Durability）指已提交的事务修改数据会被持久保存。 GraalVM Native Image(Alpha) 背景信息 本节主要介绍如何通过 GraalVM 的 native-image 组件构建 ShardingSphere‐Proxy 的 Native Image 和对应的 Docker Image 。 注意事项 • ShardingSphere Proxy 尚未准备好与 GraalVM Native Image 集成。其在 https://github

4.1 背景 数据库事务需要满足 ACID（原子性、一致性、隔离性、持久性）四个特性。 • 原子性（Atomicity）指事务作为整体来执行，要么全部执行，要么全不执行； • 一致性（Consistency）指事务应确保数据从一个一致的状态转变为另一个一致的状态； • 隔离性（Isolation）指多个事务并发执行时，一个事务的执行不应影响其他事务的执行； • 持久性（Durability）指已提交的事务修改数据会被持久保存。 配置项 配置项 描述 值 comp ute.image.repository ShardingSphere‐Proxy 的镜像名 apache/shar dingsphere-proxy comp ute.image.pullPolicy ShardingSphere‐Proxy 镜像拉取 策略 IfNotPresent compute.image.tag ShardingSphere‐Proxy completionDetector: COMPLETION_DETECTOR (algorithmDefinition) dataConsistencyChecker: DATA_CONSISTENCY_CHECKER (algorithmDefinition) rateLimiter: RATE_LIMITER (algorithmDefinition) streamChannel: