Chaos Testing and Engineering for large scale application

The intent of this presentation is to educate the audience on chaos engineering , role of QA and the different techniques and strategies that can be applied to achieve the path of site reliability

With the rise of micro services and cloud based infrastructure, the applications have grown increasingly complex. We all depend on these systems more than ever, yet failures have become much harder to predict. These failures cause costly outages for the organizations. The outages restrict the customers trying to access the application, transact business, and get work done. Even brief outages can impact the firms business, so the cost of downtime is becoming a important factor for many engineering teams. One outage can cost a firm millions of dollars.Companies need a solution to this challenge—waiting for the next costly outage is not an option. To meet the challenge head on, more and more companies are turning to Chaos Engineering.Chaos Engineering is a disciplined approach to identifying failures before they become outages. By proactively testing how a system responds under stress, you can identify and fix failures before they turn into a disaster. This presentation will provide details regarding the different techniques that can be applied to the break things on purpose which will help your applications increased availability, lower mean time to resolution (MTTR), lower mean time to detection (MTTD), fewer bugs shipped to product, and fewer outages. It will also discuss the role of QA in chaos engineering and how they can collaborate with the architects to carry out the below experiments - Known Knowns - Known Unknowns - Unknown Knowns - Unknown Unknowns It will further discuss on how the audience((QAs) can transition from learning about Chaos Testing to practicing it. This will include how they can prepare for the Gameday and simulate a production like behavior to achieve the the path of site reliability. Finally, it will conclude with the best practices that can followed by QAs and Developer to survive an outage in production.