data ecosystems. ShardingSphere provides mi‐ gration capabilities to help users migrate the data from other data sources, while simul‐ taneously performing data sharding. Q ue ry Fe de ra ti on Federated complex data query and analysis capabilities across data sources, simpli‐ fying the data aggregation from different data locations. Da ta En cr yp ti on Data Encryption is a basic way to ensure data security optional, allowing you to choose whether to include zero or multiple components. Components are isolated from each other, and mul‐ tiple components can be used together by overlaying. It includes data sharding

data ecosystems. ShardingSphere provides mi‐ gration capabilities to help users migrate the data from other data sources, while simul‐ taneously performing data sharding. Q ue ry Fe de ra ti on Federated complex data query and analysis capabilities across data sources, simpli‐ fying the data aggregation from different data locations. Da ta En cr yp ti on Data Encryption is a basic way to ensure data security optional, allowing you to choose whether to include zero or multiple components. Components are isolated from each other, and mul‐ tiple components can be used together by overlaying. It includes data sharding

connecting data ecosystems. SharingSphere provides migra‐ tion capabilities to help users migrate the data from other data sources, while simultane‐ ously performing data sharding. Query Feder‐ ation Federated complex data query and analysis capabilities across data sources, simpli‐ fying the data aggregation from different data locations. Data En‐ cryp‐ tion Data Encryption is a basic way to ensure data security optional, allowing you to choose whether to include zero or multiple components. Components are isolated from each other, and mul‐ tiple components can be used together by overlaying. It includes data sharding

分片，并且使用 order_id 进行关联，则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联，关联查询效率将大大提升。举例说明，如果 SQL 为： SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在不配置绑定表关系时，假设分片键 片，那么 路由后的 SQL 应该为 4 条，它们呈现为笛卡尔积： SELECT i.* FROM t_order_0 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i

increment instead of a total overturn. Apache ShardingSphere begin to focus on pluggable architecture from version 5.x, features can be em‐ bedded into project flexibility. Currently, the features such as to take these pressures. Therefore, database availability has become the key to the whole system. From the aspect of operation costs, when the data in a database instance has reached above the thresh‐ native distributed NoSQL. But its incom‐ patibility with SQL and imperfection in ecosystem block it from defeating the relational database in the competition, so the relational database still holds an unshakable

分片，并且使用 order_id 进行关联，则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联，关联查询效率将大大提升。举例说明，如果 SQL 为： SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在不配置绑定表关系时，假设分片键 片，那么 路由后的 SQL 应该为 4 条，它们呈现为笛卡尔积： SELECT i.* FROM t_order_0 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i

分片，并且使用 order_id 进行关联，则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联，关联查询效率将大大提升。举例说明，如果 SQL 为： SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在不配置绑定表关系时，假设分片键 片，那么 路由后的 SQL 应该为 4 条，它们呈现为笛卡尔积： SELECT i.* FROM t_order_0 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i

friendly to DBA. DistSQL enables users to operate Apache ShardingSphere like a database, transforming it from a frame‐ work and middleware for developers to a database product for DBAs. DistSQL is divided into guarantee the quality of the project. Apache ShardingSphere begin to focus on pluggable architecture from version 5.x, features can be embedded into project flexibility. Currently, the features such as data 3.4. Pluggable Architecture 17 4 Features Apache ShardingSphere provides a variety of features, from database kernel and database distributed solution to applications closed features. There is no boundary

friendly to DBA. DistSQL enables users to operate Apache ShardingSphere like a database, transforming it from a frame‐ work and middleware for developers to a database product for DBAs. DistSQL is divided into guarantee the quality of the project. Apache ShardingSphere begin to focus on pluggable architecture from version 5.x, features can be embedded into project flexibility. Currently, the features such as data 3.4. Pluggable Architecture 17 4 Features Apache ShardingSphere provides a variety of features, from database kernel and database distributed solution to applications closed features. There is no boundary

optional, allowing you to choose whether to include zero or multiple components. Components are isolated from each other, and mul‐ tiple components can be used together by overlaying. It includes data sharding 2.2. ShardingSphere-Proxy 15 3 Features Apache ShardingSphere provides a variety of features, from database kernel and database distributed solution to applications closed features. There is no boundary to take these pressures. Therefore, database availability has become the key to the whole system. From the aspect of operation costs, when the data in a database instance has reached above the thresh‐