Chaos Engineering with Chaos Toolkit

Practical exposure using Chaos Toolkit

What you'll learn
Chaos Engineering Concept
Chaos Toolkit Installation and configuration
Create and run Chaos Toolkit experiments to break the running services
Impact of random experiments execution on application
Steady State Hypothesis - SSH in detail
Rollback of experiment execution
Abort and other failure injection in microservices using Chaos experiments
Requirements
Basic Cloud understanding
Kubernetes knowledge
Basic understanding of microservices deployment through Istioctl
Basic monitoring services using Prometheus and Grafana
Description
What you'll learn

The fundamental of chaos engineering

Why do we need chaos engineering

How to manage the destruction

How to test and find limits of a system

Step by step learning of chaos engineering with chaos toolkit by implementing practical chaos experiments

Requirements

Kubernetes cluster

A few tools installed on a laptop (instructions are provided in the course)

Description

As is often the case with new and technical areas, Chaos Engineering is a simple title for a rich and complex topic. Many of its principles and practices are counter intuitive - starting with its name, which makes it doubly challenging to explain.

I’m very pleased to say, this course would make you so easy to understand about chaos engineering, because here you will find simply explanation of chaos engineering with practical exposure, that makes it unique.

This, however, brings us to the main question. Why on earth would any reasonable person want to introduce chaos into their systems? Things are complicated enough already in our lives, so why go looking for trouble?

The short answer is that if you don’t look for trouble, you won’t be prepared when it comes looking for you. And eventually, trouble comes looking for all of us.

Testing—at least as we have all understood the term—will not be of much help. A test is an activity you run to make sure that your system behaves in a way that you expect under a specific set of conditions.

The biggest source of trouble, however, is not from the conditions we were expecting, but from the conditions that never occurred to us. No amount of testing will save us from emergent properties and behaviors. For that, we need something new.

That is chaos engineering.

Who this course is for

Newcomer as well as experienced software developers, DevOps those want their application should be safe during production.

This course is for everyone interested in learning experiment with chaos engineering with chaos toolkit.

Taking this course will enable you to be among the first to gain a very solid understanding of chaos engineering

Who this course is for
The chaos will help learner's resume shortlisted as many companies are intended to use chaos
The one who wanted to learn chaos in order to make the services more resilient and robust
The one who want to identify vulnerabilities before a hacker does or before a system failure