Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Mass data high concurrency 3.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 32 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 32 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 32 3.2.6 Related references . . . . . . . . . . . . .

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mass data high concurrency 8.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 36 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 36 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 37 8.2.6 Related references . . . . . . . . . . . . .

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Mass data high concurrency 3.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 31 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 31 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 31 3.2.6 Related references . . . . . . . . . . . . .

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8.1.4 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mass data high concurrency 8.2.5 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Application Scenarios for ShardingSphere XA Transactions . . . . . . . . . . . . 36 Application Scenarios Scenarios for ShardingSphere BASE Transaction . . . . . . . . . . . 36 Application Scenarios for ShardingSphere LOCAL Transaction . . . . . . . . . . 37 8.2.6 Related references . . . . . . . . . . . . .

SQL databases and objects in Java, .NET, and Ruby on Rails. The mappings are decoupled from the application logic by packaging the SQL statements in XML configuration files. It abstracts almost all of the Interfaces − MyBatis provides database-independent interfaces and APIs that help the rest of the application remain independent of any persistence-related resources. Open source− MyBatis is free and an open the form of stored procedures so that business logic can be kept out of the database, and the application is more portable and easier to deploy and test. Supports inline SQL − No pre-compiler is needed

distributed database access application with the database. Focusing on interaction, it effectively organizes the interaction between messy applications and the database. The application and database that use high‐performance light‐weight OLTP application developed with Java; ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and unified sharding strategy by the same registry center, ShardingSphere can build an application system applicable to all kinds of scenarios. Architects can adjust the system architecture to

high‐performance light‐weight OLTP application developed with Java. ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and a unified sharding strategy by the same registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture High loss Decentralization Yes No Static Entry No Yes ShardingSphere‐JDBC is suitable for java application. 3.1.2 ShardingSphere-Proxy ShardingSphere‐Proxy is the second product of Apache ShardingSphere

high‐performance light‐weight OLTP application developed with Java. ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and a unified sharding strategy by the same registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture High loss Decentralization Yes No Static Entry No Yes ShardingSphere‐JDBC is suitable for java application. 3.1.2 ShardingSphere-Proxy ShardingSphere‐Proxy is the second product of Apache ShardingSphere

high‐performance light‐weight OLTP application developed with Java. ShardingSphere‐Proxy provides static entry and all languages support, applicable for OLAP application and the sharding databases management ShardingSphere‐Proxy and a unified sharding strategy by the same registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture Notice: Please change ${latest.release.version} to the actual version. 3. Edit application.yml. spring: shardingsphere: datasource: names: ds_0, ds_1 ds_0: type: com.zaxxer.hikari

你会想在命名空间 中共享相同的缓存配置和实例。在这样的 情况下你可以使用 cache-ref 元素来引用另外一个缓存。 Copyright © 2010–2015 MyBatis.org. All rights reserved. Your visitors can 理解关于目录结构的最佳实践是很重要的。MyBatis 非常灵 活, 你可以用你自己的文件来做几乎所有的事 情。 但是对于任一框架, 都有一些最佳的方式。 让我们看一下典型应用的目录结构: /my_application /bin /devlib /lib <-- MyBatis *.jar文件在这里。 文件在这里。 /src /org/myapp/ 最近更新: 24 五月 2015 最近更新: 24 五月 2015 || 版本: 3.3.0 版本: 3.3.0 Do you need professional PDFs for your application? Try the PDFmyURL HTML to PDF API! /test /org/myapp/ /action /data