. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

About Data Consistency in Cassandra 58 Tunable Consistency for Client Requests 58 About Write Consistency 58 About Read Consistency 58 Choosing Client Consistency Levels 59 Consistency Levels for for Multi-Data Center Clusters 59 Specifying Client Consistency Levels 60 About Cassandra's Built-in Consistency Repair Features 60 Cassandra Client APIs 60 About Cassandra CLI 60 About CQL 61 Other Lexical Structure 99 CQL Identifiers and Keywords 100 CQL Constants 100 CQL Comments 100 CQL Consistency Levels 100 CQL Data Types 101 Working with Dates and Times 101 CQL Storage Parameters 102 CQL

Processing (HTAP) workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability. The goal of TiDB is to provide users with a one-stop database solution HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. 2.1.1 Key features • Horizontally scaling out or scaling in easily The requirements for data consistency, reliability, availability, scalability, and disaster tolerance As we all know, the financial industry has high requirements for data consistency, reliability, availability

Processing (HTAP) workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability. The goal of TiDB is to provide users with a one-stop database solution HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key features of TiDB. 2.1.1 Key features requirements for data consistency, reliability, availability, scalability, and disaster tolerance As we all know, the financial industry has high requirements for data consistency, reliability, availability