Flexible adaptation of database protocol, SQL dialect and database storage. It can quickly link applications and multi‐mode heterogeneous databases quickly. • Enhance: Capture database access entry to provide MySQL or PostgreSQL protocol to operate data, which is friendlier to DBAs • Transparent towards applications, it can be used directly as MySQL and PostgreSQL servers. • Applicable to any kind of terminal distributed data‐access applications with the databases. Focusing on interaction, it effectively organizes the interaction between messy applications and databases. The applications and databases that use

Flexible adaptation of database protocol, SQL dialect and database storage. It can quickly connect applications and heterogeneous databases quickly. • Enhance: Capture database access entry to provide additional MySQL or PostgreSQL protocol to operate data, which is friendlier to DBAs. • Transparent towards applications, it can be used directly as MySQL and PostgreSQL servers; • Applicable to any kind of terminal distributed data‐access applications with the databases. Focusing on interaction, it effectively organizes the interaction between messy applications and databases. The applications and databases that use

Flexible adaptation of database protocol, SQL dialect and database storage. It can quickly connect applications and heterogeneous databases quickly. • Enhance: Capture database access entry to provide additional MySQL or PostgreSQL protocol to operate data, which is friendlier to DBAs. • Transparent towards applications, it can be used directly as MySQL and PostgreSQL servers; • Applicable to any kind of terminal distributed data‐access applications with the databases. Focusing on interaction, it effectively organizes the interaction between messy applications and databases. The applications and databases that use

KEY" columns by auto- matically adjusting the values during sync to ensure uniqueness. For most applications, this provides the desired behavior. In cases where this approach will not work, the behavior the largest value in the table prior to the INSERT2, or if the table was empty, 1. But in a decentralized environment like Zumero, this approach is likely to cause unique constraint viola- tions on the KEY columns during sync to ensure that they are unique. This approach is compatible with most applications. Specifically, it should work for you as long as you are complying with the following guidelines

Workbench, etc.) that is compatible of MySQL protocol to operate data. • Totally transparent to applications, it can be used directly as MySQL. • Applicable to any kind of terminal that is compatible with the database. Focusing on interaction, it effectively organizes the interaction between messy applications and the database. The application and database that use Database Mesh to visit database will centralization Yes No No Static Entry No Yes No 1.1.4 Hybrid Architecture ShardingSphere‐JDBC adopts decentralized architecture, applicable to high‐performance light‐weight OLTP application developed with Java;

management, and can automatic operation by simply adding servers. ElasticJob is a lightweight, decentralized solution that provides distributed task sharding services. 2 2 Features • Elastic Schedule Java’ s SPI mechanism. 5.5. Job Open Ecosystem 18 6 User Manual ElasticJob is a lightweight, decentralized solution that provides distributed task sharding services. The advantages of ElasticJob are no code or Spring XML file, but the registry center is not updated? Answer: ElasticJob adopts a decentralized design. If the configuration of each client is inconsistent and is not controlled, the configuration

top of multi‐modal heterogeneous databases, while providing standardized connec‐ tion mode for applications through built‐in DistSQL. 1.2.2 Enhance: Database computing enhancement engine It can further MySQL or PostgreSQL pro‐ tocol to operate data, which is more friendly to DBAs. • Transparent to applications, it can be used directly as MySQL/PostgreSQL; • Compatible with MySQL‐based databases, such as Yes Hybrid Architecture ShardingSphere‐JDBC adopts a decentralized architecture, applicable to high‐performance light‐weight OLTP applications developed with Java. ShardingSphere‐Proxy provides static

top of multi‐modal heterogeneous databases, while providing standardized connec‐ tion mode for applications through built‐in DistSQL. 1.2.2 Enhance: Database computing enhancement engine It can further MySQL or PostgreSQL pro‐ tocol to operate data, which is more friendly to DBAs. • Transparent to applications, it can be used directly as MySQL/PostgreSQL; • Compatible with MySQL‐based databases, such as 1.3.3 Hybrid Architecture ShardingSphere‐JDBC adopts a decentralized architecture, applicable to high‐performance light‐weight OLTP applications developed with Java. ShardingSphere‐Proxy provides static

top of multi‐modal heterogeneous databases, while providing standardized connec‐ tion mode for applications through built‐in DistSQL. 2.2 Enhance: Database computing enhancement engine It can further MySQL or PostgreSQL pro‐ tocol to operate data, which is more friendly to DBAs. • Transparent to applications, it can be used directly as MySQL/PostgreSQL; • Compatible with MySQL‐based databases, such as 3.3 Hybrid Architecture ShardingSphere‐JDBC adopts a decentralized architecture, applicable to high‐performance light‐weight OLTP applications developed with Java. ShardingSphere‐Proxy provides static

top of multi‐modal heterogeneous databases, while providing standardized connec‐ tion mode for applications through built‐in DistSQL. 2.2 Enhance: Database computing enhancement engine It can further MySQL or PostgreSQL pro‐ tocol to operate data, which is more friendly to DBAs. • Transparent to applications, it can be used directly as MySQL/PostgreSQL; • Compatible with MySQL‐based databases, such as 3.3 Hybrid Architecture ShardingSphere‐JDBC adopts a decentralized architecture, applicable to high‐performance light‐weight OLTP applications developed with Java. ShardingSphere‐Proxy provides static