http://www.tutorialspoint.com/mybatis/mybatis_quick_guide.htm Copyright © tutorialspoint.com MYBATIS - QUICK GUIDE MYBATIS - QUICK GUIDE MYBATIS - OVERVIEW MYBATIS - OVERVIEW MyBatis is an open source

. . . . . . . . . . . . . . . . . . . . 55 iv Monitoring panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Monitoring application performance . . . . . . . . . . . . . engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 11.5.2 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 Test case configuration environment type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 11.8.3 User guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 Environment setup

. . . . . . . . . . . . . . . . . . . . 55 iv Monitoring panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Monitoring application performance . . . . . . . . . . . . . engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 11.5.2 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 Test case configuration environment type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 11.8.3 User guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Environment setup

. . . . . . . . . . . . . . . . . . . . . . 52 Monitoring panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Monitoring application performance . . . . . . . . . . . . . engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 6.5.2 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Test case configuration Test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 6.8.3 User guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Environment setup

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 6.3.1 Deploy Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Application deployment 6.3.3 Execution Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Monitoring job server alive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 6.3.4 Console corresponding time point is reached. The registration cen‐ ter is only used for job registration and monitoring information storage. The main job node is only used to handle functions such as sharding and cleaning

. . . . . . . . . . . . . . . . . . . . . . 51 Monitoring panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Monitoring application performance . . . . . . . . . . . . . engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 x 6.5.2 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Test case configuration Test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 6.8.3 User guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Environment setup

Challenges There is no unified database access protocol and SQL dialect, as well as the maintenance and monitoring methods differences by various databases, learning and maintenance cost of developers and DBAs logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting, storing and analyzing analyzing the observable data of the system. Its main functions include per‐ formance index monitoring, call stack analysis, service topology, etc. Apache ShardingSphere is not responsible for gathering, storing

Challenges There is no unified database access protocol and SQL dialect, as well as the maintenance and monitoring methods differences by various databases, learning and maintenance cost of developers and DBAs logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting, storing and analyzing analyzing the observable data of the system. Its main functions include per‐ formance index monitoring, call stack analysis, service topology, etc. Apache ShardingSphere is not responsible for gathering, storing

Challenges There is no unified database access protocol and SQL dialect, as well as the maintenance and monitoring methods differences by various databases, learning and maintenance cost of developers and DBAs configurations in the config center will immediately take effect in the producing environment. Operation Guide Circuit Breaker Write DISABLED (case insensitive) to IP@PORT to disable that instance; delete DISABLED APM Integration APM Integration Background APM is the abbreviation for application performance monitoring. Currently, main APM functions lie in the performance diagnosis of distributed systems, including

Hint Sharding Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.5 Guide to Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 SQL Parsing . route to the designated node. 3.1. Sharding 21 Apache ShardingSphere document, v5.0.0-beta 3.1.5 Guide to Kernel The major sharding processes of all the three ShardingSphere products are identical. The configurations in the config center will immediately take effect in the producing environment. Operation Guide Circuit Breaker Write DISABLED (case insensitive) to IP@PID@UUID to disable that instance; delete