{"id":12254,"date":"2020-08-05T06:23:14","date_gmt":"2020-08-05T10:23:14","guid":{"rendered":"https:\/\/origin-www.parsons.com\/?p=12254"},"modified":"2022-10-05T13:22:31","modified_gmt":"2022-10-05T17:22:31","slug":"chaos-engineering-instrumenting-failure-to-prevent-failure","status":"publish","type":"post","link":"https:\/\/www.parsons.com\/2020\/08\/chaos-engineering-instrumenting-failure-to-prevent-failure\/","title":{"rendered":"Chaos Engineering \u2013 Instrumenting Failure To Prevent Failure"},"content":{"rendered":"\n
\"Mental<\/figure>\n\n\n\n

Chaos Engineering is a modern software development practice pioneered by Netflix, which intentionally injects controlled failures into a system to test the resiliency and second-order effects of given failure cases. <\/p>\n\n\n\n

While deployment of systems into The Cloud is intended to solve some of these problems, unexpected outages do occur and have caused billions of dollars in losses as recently as April 2011, when a configuration error in an AWS Availability Zone caused the network connectivity to failover to the wrong link, causing cascading failures within the entire region. Hundreds of companies were offline or experienced severely degraded service during the outage. <\/p>\n\n\n\n

Critics say the real responsibility lies with those companies – the applications running on the AWS infrastructure were never properly tested for such a failure. Designing for failure may save those organizations which are increasingly reliant on cloud infrastructure. <\/p>\n\n\n\n

How did Netflix weather the April 2011 outage? Well enough<\/a>. Netflix \u201cChaos Monkey,\u201d and larger \u201cSimian Army\u201d services constantly inject failure conditions into their production infrastructure. When Netflix noticed increasing failure in the affected region, they were able to shift their workloads to unaffected regions in an expedient manner with minimal disruption to their customers. <\/p>\n\n\n\n

Jenn Bergstrom takes us on a tour of the history of Chaos Engineering, where we\u2019re implementing it here at Parsons, and how you can use Chaos Engineering as a force-multiplier for assessing risk in software development. One thing is for certain \u2013 Failures will happen. Will your system survive them?<\/p>\n\n\n\n

Meet the Presenter<\/strong><\/h3>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n

Jenn Bergstrom is a software engineer at Parsons. She came to Parsons through an acquisition as an enterprise-scale Java application developer and has supported a broad range of projects within the company. Jenn has nine AWS Certifications and an Azure certification. She builds secure cloud-agnostic solutions for internal and external customers and uses DevSecOps and Chaos Engineering to prove out the reliability and interoperability of the solutions. In her free time, Jenn enjoys creating art and music and cheering her kiddos on in their endeavors.<\/p>\n\n\n\n

Watch The Webinar:<\/h3>\n\n\n\n
\n