frameworks such as Hibernate typically uses a custom query language i.e. the Hibernate Query Language HQL or Enterprise JavaBeans Query Language EJBQL. MYBATIS Design Features MyBatis comes with the following can to facilitate hyper-fast development. Portability − MyBatis can be implemented for nearly any language or platform such as Java, Ruby, and C# for Microsoft .NET. Independent Interfaces − MyBatis provides join fetching, caching, runtime code generation, and inheritance. MyBatis uses JAVA programming language while developing database oriented application. Before proceeding further, make sure that you understand

ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry the preferred method according to their re‐ quirements. 2.1.2 Limitations Currently only Java language is supported. 2.1.3 Requirements The development environment requires Java JRE 8 or later. 2

ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry the preferred method according to their re‐ quirements. 2.1.2 Limitations Currently only Java language is supported. 2.1.3 Requirements The development environment requires Java JRE 8 or later. 2

distributed governance, applicable in a variety of situations such as Java isomorphism, heterogeneous language and Cloud‐Native. As the cornerstone of enterprises, the relational database has a huge market the preferred method according to their re‐ quirements. 2.1.2 Limitations Currently only Java language is supported. 2.1.3 Requirements The development environment requires Java JRE 8 or later. 2 distributed governance, applicable in a variety of situations such as Java isomorphism, heterogeneous language and Cloud‐ Native. 3.1.1 ShardingSphere-JDBC As the first product and the predecessor of Apache

ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry choose the preferred method according to their requirements. 7.1.2 Limitations Currently only Java language is supported. 7.1.3 Requirements The development environment requires Java JRE 8 or later. 7

ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry ShardingSphere-Proxy Database Any MySQL/PostgreSQL Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry choose the preferred method according to their requirements. 7.1.2 Limitations Currently only Java language is supported. 7.1.3 Requirements The development environment requires Java JRE 8 or later. 7

distributed governance, applicable in a variety of situations such as Java isomorphism, heterogeneous language and Cloud‐Native. As the cornerstone of enterprises, the relational database has a huge market distributed governance, applicable in a variety of situations such as Java isomorphism, heterogeneous language and Cloud‐ Native. 3.1.1 ShardingSphere-JDBC As the first product and the predecessor of Apache RQL and RAL. • RDL (Resource & Rule Definition Language) responsible for the definition of resources and rules; • RQL (Resource & Rule Query Language) responsible for the query of resources and rules;

功能特色 • RDL（Resource & Rule Definition Language）负责资源 和规则的创建、修改和删除； • RQL（Resource & Rule Query Language）负责资源和规 则的查询和展现； • RAL（Resource & Rule Administration Language）负责 Hint、事务类型切换、分片执行计划查询等增量功能的操作。

WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # ## @section Governance-Node parameters v5.2.0 RDL Resource & Rule Definition Language，负责资源和规则的创建、修改和删除。 RQL Resource & Rule Query Language，负责资源和规则的查询和展现。 RAL Resource & Rule Administration Language，负责强制路由、熔断、配置导入导出、数据迁移控制等管理 功能。 RUL Resource & Rule Utility Language，负责 SQL 解析、SQL 格式化、执行计划预览等功能。 对系统的影响 之前 在拥有 DistSQL 以前，用户一边使用 SQL 语句操作数据，一边使用 YAML 文件来管理 ShardingSphere 的配置，如下图： 这时用户不得不面对以下几个问题：‐ 需要通过不同类型的客户端来操作数据和管理 ShardingSphere

三种类型。 • RDL（Resource & Rule Definition Language）负责资源和规则的创建、修改和删除； • RQL（Resource & Rule Query Language）负责资源和规则的查询和展现； • RAL（Resource & Rule Administration Language）负责 Hint、事务类型切换、分片执行计划查询 等管理功能。 3.3 CREATE FOREIGN DATA WRAPPER alt_fdw1 CREATE SERVER alt_fserv1 FOREIGN DATA WRAPPER alt_fdw1 CREATE LANGUAGE alt_lang1 HANDLER plpgsql_call_handler CREATE STATISTICS alt_stat1 ON a, b FROM alt_regress_1 CREATE FOREIGN DATA WRAPPER alt_fdw1 CREATE SERVER alt_fserv1 FOREIGN DATA WRAPPER alt_fdw1 CREATE LANGUAGE alt_lang1 HANDLER plpgsql_call_handler CREATE STATISTICS alt_stat1 ON a, b FROM alt_regress_1