be saved persistently. In single data node, transactions are only restricted to the access and control of single database re‐ sources, called local transactions. Almost all the mature relational databases application scenario. However, in distributed scenarios, traditional database solutions cannot manage and control global transactions, and users may find data inconsistency on multiple database nodes. ShardingSphere database has become a trend gradually. The unified management ability of cluster perspective, and control ability of individual components are necessary ability in modern database system. 3.6.2 Challenges

sets to output through unified JDBC interface. Result merger in‐ cludes methods as stream merger, memory merger and addition merger using decorator merger. Parse Engine Compared to other programming languages operations, including the SET database manage‐ ment order used to set the database and transaction control statement as TCL. In this case, all physical databases matched with the name are traversed according and ORDER BY to GROUP BY SQL, and they are used to transfer memory merger to stream merger. In the result merger part, stream merger and memory merger will be explained in detail. The overall structure

be saved persistently. In single data node, transactions are only restricted to the access and control of single database re‐ sources, called local transactions. Almost all the mature relational databases application scenario. However, in distributed scenarios, traditional database solutions cannot manage and control global transactions, and users may find data inconsistency on multiple database nodes. ShardingSphere database has become a trend gradually. The unified management ability of cluster perspective, and control ability of individual components are necessary ability in modern database system. 3.6.2 Challenges

be saved persistently. In single data node, transactions are only restricted to the access and control of single database re‐ sources, called local transactions. Almost all the mature relational databases application scenario. However, in distributed scenarios, traditional database solutions cannot manage and control global transactions, and users may find data inconsistency on multiple database nodes. ShardingSphere database has become a trend gradually. The unified management ability of cluster perspective, and control ability of individual components are necessary ability in modern database system. 8.5.2 Challenges

1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2.2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone Apache shardingsphere provides various mode such as memory, stand‐alone and cluster. 3.2. Mode 13 Apache ShardingSphere document, v5.1.1 3.2.2 Memory mode Suitable for fast integration testing, which database has become a trend gradually. The unified management ability of cluster perspective, and control ability of individual components are necessary ability in modern database system. 4.2.2 Challenges

be saved persistently. In single data node, transactions are only restricted to the access and control of single database re‐ sources, called local transactions. Almost all the mature relational databases application scenario. However, in distributed scenarios, traditional database solutions cannot manage and control global transactions, and users may find data inconsistency on multiple database nodes. ShardingSphere database has become a trend gradually. The unified management ability of cluster perspective, and control ability of individual components are necessary ability in modern database system. 8.5.2 Challenges

1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2.2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone Apache shardingsphere provides various mode such as memory, stand‐alone and cluster. 3.2. Mode 13 Apache ShardingSphere document, v5.0.0 3.2.2 Memory mode Suitable for fast integration testing, which process + merger ordering to avoid excessive memory occupation. SQL rewrite unavoidably occupies extra bandwidth, but it will not lead to sharp increase of memory occupation. Most people may assume that

1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2.2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone Apache shardingsphere provides various mode such as memory, stand‐alone and cluster. 3.2. Mode 13 Apache ShardingSphere document, v5.1.2 3.2.2 Memory mode Suitable for fast integration testing, which database has become a trend gradually. The unified management ability of cluster perspective, and control ability of individual components are necessary ability in modern database system. 4.2.2 Challenges

zookeep er. resources.limits ZooKeeper 容器的资源限制 {} govern ance.zookeeper. resour ces.requests. memory ZooKeeper 容器申请的内存 “ 256Mi“ gov ernance.zookeeper. res ources.requests.cpu ZooKeeper 容器申请的 cpu 拉取私有仓库的凭证 [] comp ute.resources.limits ShardingSphere‐Proxy 容器的资 源限制 {} compute.resou rces. requests.memory ShardingSphere‐Proxy 容器申请 的内存 2Gi compute.re sources. requests.cpu ShardingSphere‐Proxy 容器申请 limits for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.memory The requested memory for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.cpu The

zookeep er. resources.limits ZooKeeper 容器的资源限制 {} govern ance.zookeeper. resour ces.requests. memory ZooKeeper 容器申请的内存 “ 256Mi“ gov ernance.zookeeper. res ources.requests.cpu ZooKeeper 容器申请的 cpu 拉取私有仓库的凭证 [] comp ute.resources.limits ShardingSphere‐Proxy 容器的资 源限制 {} compute.resou rces. requests.memory ShardingSphere‐Proxy 容器申请 的内存 2Gi compute.re sources. requests.cpu ShardingSphere‐Proxy 容器申请 limits for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.memory The requested memory for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.cpu The