including 3 independent products: JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of situations such SQL Dialect Translate (TODO) Observ ability Distributed Transaction SQL Audit (TODO) Elastic Scale‐out SQL Firewall (TODO) Highly Available 1.2. Solution 5 Apache ShardingSphere document, v5.0 independent products: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of situations such

including 3 independent products: JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of situations such SQL Dialect Translate (TODO) Observ ability Distributed Transaction SQL Audit (TODO) Elastic Scale‐out SQL Firewall (TODO) Highly Available 1.2. Solution 5 Apache ShardingSphere document, v5.1 independent products: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of situations such

including 3 independent products: JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of situations such SQL Dialect Translate (TODO) Observ ability Distributed Transaction SQL Audit (TODO) Elastic Scale‐out SQL Firewall (TODO) Highly Available 1.2. Solution 5 Apache ShardingSphere document, v5.1 independent products: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of situations such

including 3 independent products, JDBC, Proxy & Sidecar (Planning). They all provide functions of data scale out, distributed transaction and distributed governance, applicable in a variety of situa‐ tions transaction • BASE transaction 1.2.3 Database Governance • Distributed Governance • Data migration & Scale out • Tracing & Observability Supported • Data Encryption 1.2. Features 4 2 Quick Start In shortest solution according to current situations. Automatic execution engine has narrowed the selection scale of connection mode to each SQL opera‐ tion. Aiming at each SQL request, automatic execution engine

ElasticJob can make developers no longer worry about the non‐functional requirements such as jobs scale out, so that they can focus more on business coding; At the same time, it can release operators too Features • Elastic Schedule – Support job sharding and high availability in distributed system – Scale out for throughput and efficiency improvement – Job processing capacity is flexible and scalable Schedule API • ☐ Unified Resource API • � Distributed Features – � High Availability – � Elastic scale in/out – � Failover – � Misfire – � Idempotency – � Reconcile • � Registry Center – � ZooKeeper

massive data storage and computing. Shard‐ ingSphere provides distributed database solutions that can scale out computing and stor‐ age levels on top of the underlying database. Dis‐ tributed Trans‐ action independent clients: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of scenarios such transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because their performance cannot meet the needs in scenarios with high concurrency, and most of them

ingSphere provides a distributed database solution based on the underlying database, which can scale computing and storage horizontally. Dis‐ tributed Trans‐ action Transactional capability is key independent clients: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of scenarios such transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because their performance cannot meet the needs in scenarios with high concurrency, and most of them

ingSphere provides a distributed database solution based on the underlying database, which can scale computing and storage horizontally. D is tr ib ut ed T ra ns ac ti on Transactional capability independent clients: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of scenarios such transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because their performance cannot meet the needs in scenarios with high concurrency, and most of them

ingSphere provides a distributed database solution based on the underlying database, which can scale computing and storage horizontally. D is tr ib ut ed T ra ns ac ti on Transactional capability independent clients: ShardingSphere‐JDBC & ShardingSphere‐ Proxy. They all provide functions of data scale‐out, distributed transaction and distributed governance, applicable in a variety of scenarios such transaction consistency. The XA‐based distributed transactions are not used by Internet giants on a large scale because their performance cannot meet the needs in scenarios with high concurrency, and most of them

Schedule API • ☐ Unified Resource API • � Distributed Features – � High Availability – � Elastic scale in/out – � Failover – � Misfire – � Idempotency – � Reconcile • � Registry Center – � ZooKeeper