Level-up your testing with Chaos Engineering. Learn how pushing your programs to failure can help you plan your improvements.

DevOps for Developers

Let’s face it, bad things happen in software engineering, often when you least expect it. Servers go down, there are spikes in traffic, you receive networking errors. Luckily, you can avoid these problems. Enter chaos engineering.
Chaos engineering is where you try to find the limits of a system and simulate adverse effects that might happen. These simulations then help you to determine the best way to improve your system and build up its resiliency.
This course is divided into various sections to get you used to the different types of experiments you can run in chaos engineering. You will start by learning how to destroy application instances in order to show you the importance of scaling, fault tolerance, and high availability.
You will then dive deep into other types of experiments such as destroying a network, draining and deleting nodes, and testing availability. Towards the end of the course, you will learn how to run experiments in a Kubernetes cluster.

Kubernetes Chaos Engineering

Before we dive deeper into chaos engineering, let me introduce you to the team: me, Viktor, and another guy, Darin.

# Who is Viktor?

Let's start with me. My name is Viktor Farcic. I currently work in [CloudBees](https://www.cloudbees.com/). However, things are changing, and by the time you are reading this, I might be working somewhere else. Change is constant, and one can never know what the future brings. At the time of this writing, I am a *principal software delivery strategist and developer advocate*. It’s a very long title and, to be honest, I don’t like it because it is too long to memorize. But that’s what I am, officially.


What else can I say about myself? I am a member of the [Google Developer Experts (GDE)](https://developers.google.com/community/experts) group, and I'm one of the [Docker Captains](https://www.docker.com/community/captains). You can probably guess from those credentials that I focus on containers, Cloud, Kubernetes, and a few other things.


I’m a published author. I have written quite a few books under the umbrella of [The DevOps Toolkit Series](https://www.devopstoolkitseries.com/). I also wrote [DevOps Paradox](https://amzn.to/2myrYYA) and [Test-Driven Java Development](http://www.amazon.com/Test-Driven-Java-Development-Viktor-Farcic-ebook/dp/B00YSIM3SC). Besides those, I have done a few [Udemy courses](https://www.udemy.com/user/viktor-farcic/).

I am very passionate about DevOps, Kubernetes, microservices, continuous integration, continuous delivery, and many other topics. I prefer coding in Go.

I speak in a lot of conferences and community gatherings, and I hold a lot of workshops.


I have a blog called [TechnologyConversations.com](https://technologyconversations.com/) where I keep my random thoughts, and I co-host a podcast called [DevOps Paradox](https://www.devopsparadox.com/).

What really matters is that I’m curious about technology, and what I do changes often. A significant portion of my time is spent helping others (individuals, communities, or companies).

Now, you will meet the second person involved in the creation of this course. His name is Darin, and I will let him introduce himself.


# Who is Darin?

My name is Darin Pope. I'm currently working at [CloudBees](https://www.cloudbees.com/) as a professional services consultant. Along with Viktor, I'm the co-host of [DevOps Paradox](https://www.devopsparadox.com/). 

Whether it's figuring out the latest changes with Kubernetes or creating more content to share with our listeners and viewers, I'm always learning. Always have, always will.

---

In the next lesson, we will discuss the principles behind chaos engineering.

This lesson introduces both of the authors of this course: Viktor and Darin.


Who Are We?