Explore the principles of Chaos Engineering in this 40-minute Devoxx conference talk. Discover how Netflix improves software reliability by running experiments and injecting failures into their production system. Learn about the challenges of developing software with fallible humans and unreliable infrastructure, and how Chaos Engineering can increase confidence in complex distributed systems. Delve into the four key principles: building hypotheses around steady-state behavior, varying real-world events, running experiments in production, and automating continuous testing. Gain insights into why frequent, controlled failures can lead to improved availability and how this approach can be applied to enhance the resilience of large-scale networked services.
Overview
Syllabus
Programmers: Stop Calling Yourselves Engineers
A way to improve availability is to install proven hardware and software, and then leave it alone
If it hurts, do it more frequently, and bring the pain forward
Experiment on a distributed system in order to build confidence in the system's capability to withstand turbulent conditions in production.
Four principles of chaos engineering
Build a hypothesis around steady-state behavior
Vary real-world events
Run experiments in production
Automate experiments to run continuously
Principles recap
Taught by
Devoxx
Related Courses
-
Chaos Engineering in Action - Building Fault-Tolerant Systems
-
Chaos Engineering Primer
-
Chaos Engineering - Withstanding Turbulent Conditions in Production
-
Practical Chaos Engineering - Breaking Things on Purpose to Make Them More Resilient Against Failure
-
Principles of Chaos Engineering
-
Antics, Drift, and Chaos
