Session: Resilience Engineering: Why Break your Software with Chaos Engineering?
Web applications live in an imperfect world in which outages are around the corner. Recording, triaging, tracking, and measure the incidents that impact our applications is difficult, time-consuming, and requires talent and experienced engineering. Aware of this, Chaos Engineering introduces the injection of failures as a discipline for building confidence in the resilience capability of the systems.. We would like to tell about our journey, sharing our experience, what we learned and the challenges that we identified.
Bio
Software and Chaos Engineer Advocate. Loves building software applications, reading blogs, writing articles, solving hard performance and resilience issues and teaching software concepts.
--
Software and Devops Engineer with 6+ years of experience designing, implementing and managing the development of software applications using agile methodologies such as scrum and kanban. 1+ years of hands-on experience supporting, automating and optimizing mission-critical deployments. Experience with on-premise and cloud architectures and foundations both on the coding and deploying systems.
Professor of Software Engineering and Researcher with interest in solving performance, resilience and reliability issues, using chaos engineering and studying human factors, safety on systems and lack of monitoring and observability.