Chaos Engineering

Chaos engineering is the discipline of experimenting on a system in order to build confidence in the system's capability to withstand turbulent conditions in production.

Concept

In software development, a given software system's ability to tolerate failures while still ensuring adequate quality of service—often generalized as ''resiliency''—is typically specified as a requirement. However, development teams often fail to meet this requirement due to factors such as short deadlines or lack of knowledge of the field. Chaos engineering is a technique to meet the resilience requirement.

Chaos engineering can be used to achieve resilience against infrastructure failures, network failures, and application failures.

Operational readiness using chaos engineering

Calculating how much confidence we can have in the interconnected complex systems those put into production environment requires operational readiness metrics. Operational readiness can be evaluated using chaos engineering simulations supported by Kubernetes infrastructure in big data. Solutions for operational readiness of a platform stands for strengthening the backup, restore, network file transfer, failover capabilities and overall security. Gautam Siwach et al, performed evaluation of inducing chaos to a Kubernetes environment which terminates random pods with data from edge devices in data centers while processing analytics on big data network and infer the recovery time of pods to calculate an estimated response time.

History

2003 – Amazon

While working to improve website reliability at Amazon, Jesse Robbins created "GameDay", an initiative that increases reliability by purposefully creating major failures on a regular basis. Robbins has said GameDay was inspired by firefighter training and research in other fields lessons in complex systems, reliability engineering.

2006 – Google

While at Google, Kripa Krishnan created a similar program to Amazon's GameDay called "DiRT".

2011 – Netflix

While overseeing Netflix's migration to the cloud in 2011 Nora Jones, Casey Rosenthal, and Greg Orzell expanded the discipline while working together at Netflix by setting up a tool that would cause breakdowns in their production environment, the environment used by Netflix customers. The intent was to move from a development model that assumed no breakdowns to a model where breakdowns were considered to be inevitable, driving developers to consider built-in resilience to be an obligation rather than an option:

"At Netflix, our culture of freedom and responsibility led us not to force engineers to design their code in a specific way. Instead, we discovered that we could align our teams around the notion of infrastructure resilience by isolating the problems created by server neutralization and pushing them to the extreme. We have created Chaos Monkey, a program that randomly chooses a server and disables it during its usual hours of activity. Some will find that crazy, but we could not depend on the random occurrence of an event to test our behavior in the face of the very consequences of this event. Knowing that this would happen frequently has created a strong alignment among engineers to build redundancy and process automation to survive such incidents, without impacting the millions of Netflix users. Chaos Monkey is one of our most effective tools to improve the quality of our services."

By regularly "killing" random instances of a software service, it was possible to test a redundant architecture to verify that a server failure did not noticeably impact customers.

The concept of chaos engineering is close to the one of Phoenix Servers, first introduced by Martin Fowler in 2012.

Chaos engineering tools

Chaos Monkey

Chaos Monkey is a tool invented in 2011 by Netflix to test the resilience of its IT infrastructure. It works by intentionally disabling computers in Netflix's production network to test how remaining systems respond to the outage. Chaos Monkey is now part of a larger suite of tools called the Simian Army designed to simulate and test responses to various system failures and edge cases.

The code behind Chaos Monkey was released by Netflix in 2012 under an Apache 2.0 license.

The name "Chaos Monkey" is explained in the book '' Chaos Monkeys'' by Antonio Garcia Martinez:

Imagine a monkey entering a 'data center', these 'farms' of servers that host all the critical functions of our online activities. The monkey randomly rips cables, destroys devices and returns everything that passes by the hand .e. flings excrement The challenge for IT managers is to design the information system they are responsible for so that it can work despite these monkeys, which no one ever knows when they arrive and what they will destroy.

Simian Army

The Simian Army is a suite of tools developed by Netflix to test the reliability, security, or resiliency of its Amazon Web Services infrastructure and includes the following tools:

At the very top of the Simian Army hierarchy, Chaos Kong drops a full AWS "Region". Though rare, loss of an entire region does happen and Chaos Kong simulates a systems response and recovery to this type of event.

Chaos Gorilla drops a full Amazon " Availability Zone" (one or more entire data centers serving a geographical region).

Proofdock chaos engineering platform

Proofdock is a chaos engineering platform that focuses on and leverages the Microsoft Azure platform and the Azure DevOps services. Users can inject failures on the infrastructure, platform and application level.

Gremlin

Gremlin is a "failure-as-a-service" platform.

Facebook Storm

To prepare for the loss of a datacenter, Facebook regularly tests the resistance of its infrastructures to extreme events. Known as the Storm Project, the program simulates massive data center failures.

Days of Chaos

Voyages-sncf.com created a "Day of Chaos" in 2017, gamifying the simulation of pre-production failures. They presented their results at the 2017 DevOps REX conference.

See also

*Fault injection
*Fault tolerance
*Fault-tolerant computer system
*Data redundancy
*Error detection and correction
* Fall back and forward
* Grease (networking)
*Resilience (network)
*Robustness (computer science)

Notes and references

External links

Principle of Chaos Engineering
– The Chaos Engineering manifesto

Chaos Engineering
â€
Adrian Hornsby

How Chaos Engineering Practices Will Help You Design Better Software
â€
Mariano Calandra

{{Netflix

Netflix
Software development
Reliability engineering
Software testing
Software testing tools
Disaster recovery
Automation software
Software delivery methods