tuning to test tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Stress testing environment or parameter recommendations . . . . . . . . . . . . 336 Appendix . . . . . . . . . Database In the full‐link stress testing scenario, ShardingSphere shadow DB is used for providing data isolation support for complex testing work. The obtained testing result can accurately reflect the multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. In the test environment, the cost

tuning to test tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Stress testing environment or parameter recommendations . . . . . . . . . . . . 363 Appendix . . . . . . . . . encryption solution. Shadow Database In full‐link online load testing scenarios, ShardingSphere supports data isolation in com‐ plex load testing scenarios through the shadow database function. Execute your multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. 3.9. Shadow 46 Apache ShardingSphere

tuning to test tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Stress testing environment or parameter recommendations . . . . . . . . . . . . 472 Appendix . . . . . . . . . full‐link online load testing scenarios, ShardingSphere supports data isolation in com‐ plex load testing scenarios through the shadow database function. Execute your load testing scenarios in a production multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. In the test environment, the cost

tuning to test tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 Stress testing environment or parameter recommendations . . . . . . . . . . . . 501 Appendix . . . . . . . . . full‐link online load testing scenarios, ShardingSphere supports data isolation in com‐ plex load testing scenarios through the shadow database function. Execute your load testing scenarios in a production multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. In the test environment, the cost

Memory mode Suitable for fast integration testing, which is convenient for testing, such as for developers looking to perform fast integration function testing. This is the default mode of Apache ShardingSphere multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. In the test environment, if you rebuild reflect the real capacity level and performance of the system. 4.8.2 Challenges Full‐link pressure testing is a complex and huge task. Coordination and adjustments between microser‐ vices and middleware

Memory mode Suitable for fast integration testing, which is convenient for testing, such as for developers looking to perform fast integration function testing. This is the default mode of Apache ShardingSphere multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. In the test environment, the cost results obtained real capacity and performance of the system accurately. 4.9.2 Challenges pressure testing on production environment is a complex and huge task. Coordination and adjustments between microservices

Memory mode Suitable for fast integration testing, which is convenient for testing, such as for developers looking to perform fast integration function testing. This is the default mode of Apache ShardingSphere multiple ser‐ vices to be completed through a series of services and middleware calls. The pressure testing of a single service can no longer reflect the real scenario. In the test environment, the cost results obtained real capacity and performance of the system accurately. 4.9.2 Challenges pressure testing on production environment is a complex and huge task. Coordination and adjustments between microservices

106 Test Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Testing Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 iv Test Result 115 Test Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Testing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 sysbench test / resources/env-native.properties, for example: # the switch for PK, concurrent, column index testing and so on it.run.additional.cases=false # test scenarios, could define multiple rules it.scenarios=db