Talk at Kuberton, 02/03/2019 Chaos Testing of Microservices - Shalamov Maksym, Senior QA Automation Engineer

1. Chaos Testing of Microservices
by Maksym Shalamov,
Senior QA Automation

2. In this talk, we'll take a look at problems that we can face during testing micro-services
application. We'll focus on performance testing because on practice many teams exclude this
type of testing from the list of necessary tests.
Introduction

3. To be or not to be ...

4. A research process, which is conducted to determine how a system or sub-system performs
in terms of responsiveness and stability under a particular workload. It can also serve to
investigate, measure, validate or verify other quality attributes of the system, such as
scalability, reliability and resource usage.
Performance testing

5. Load - a research process, which is conducted to determine understand the behaviour of the
system under a specific load, which can be the some concurrent number of appeal on the
application performing a specific number of operations within the set duration
Stress - a research process, which is conducted to determine assesses the reliability and
stability of the system in excess of the limits of normal operation, such as for example
extreme load or infrastructure issues imitation
Stability - a research process, which is conducted to determine if the system can sustain the
continuous expected load, without performance degradation
Performance testing types

6. Scelability - a research process, which is conducted to determine understand the behaviour
of the system to measure its capability to scale up or scale out in terms of any of its non-func
Performance testing types

7. Requests per second (unit of time)
the measurement of how many requests are being sent to the target per second (unit time)
Throughput
indicates the number of transactions per second an application can handle, the amount of
transactions produced over time during a test
Error Rate
the mathematical calculation that produces a percentage of problem requests compared to
all requests
Client Metrics

8. Latency
a difference between time when request was sent and time when response has started to be
received
Response Time
a difference between time when request was sent and time when response has been fully
received
Client Metrics

9. The below metrics are usually monitored during the a performance test execution:
CPU Utilization
the amount of CPU time used by the application while processing the request
Memory Utilization
the amount of memory used by the application while processing the request
Disk utilization
a measure of how well the available data storage space is used
Network utilization
the amount of traffic on the network compared to the peak amount that the network can
support
Infrastructure Metrics

10. Tools

11. Input/Output operation issues

12. Networking operation issues

13. - Libraries
- Packаges
- 3-rd application(workers/queue managers)
Both hands are left issues

14. Monitoring

15. Debugging

16. Conclusion

17. Thank you for your attention!
Questions?

18. CONTACTS:
Email: max.newmail@gmail.com
Skype: shalamov.maxim