It’s in our nature to explore boundary and push the limits, to see just how fast we can go, how big we can build it or how strong we can make it.
‘Chaos Testing’ has emerged as an integral part of the testing methodology. It helps to verify that the applications perform well despite unprecedented events or system failures
In 2010, Netflix migrated to the cloud and the one lesson they learned along the way was that, “the best way to avoid failure is to fail constantly.”
They created a tool called “Chaos Monkey” which would induce failure by randomly killing services.
The Netflix team later released Chaos Monkey as open source software which has been widely popular and that leads to a question that poses in front of us is that, “What is the discipline of Chaos Engineering as a whole?”
The discipline of Chaos Engineering is defined as “the experimentation on a distributed system in order to build confidence in the systems capability to withstand turbulent conditions in production.”
Chaos testing involves working with a finished product in a test environment, manipulating some of the environment settings, and seeing how the product coped under pressure.
So, will you learn more about your systems by random destruction or with a methodical process?
If you are choosing a tool and working on your list of requirements your goal should be to focus on the learning aspect. Every Chaos Engineering tool can destroy things, that is what they are built for, but will that tool be conducive to learning, and help you be a more knowledgeable engineer is what you should focus on.
Learn more about Chaos Engineering at our upcoming event – TestExpo and Agile & DevOps Expo: Adaptive Challenges, 20-21 October, online (EMEA time zone) where Nikhil Barthwal, Software Engineer at Facebook will talk about “CHAOS ENGINEERING: BUILDING IMMUNITY IN PRODUCTION SYSTEMS” at his KEYNOTE.
Click here to see the full programme.
Be among the 5 lucky persons to get a free pass for the event. Register now!
