Check out the transcript and video from our conversation below.
Viktor: Jason, can you tell us a little bit about yourself? And how did you end up in this field of chaos engineering?
Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Check out the transcript and video from our conversation below.
Viktor: Jason, can you tell us a little bit about yourself? And how did you end up in this field of chaos engineering?
Chaos Engineering might sound like a buzzword - but take it from someone who used to joke his job title was Chief Chaos Engineer (more on that later) it is much more than buzz or a passing fad - it’s a practice.
The world can be a scary place and more and more companies are beginning to turn to Chaos Engineering to proactively poke and prod their systems and in doing so are improving their reliability and guarding against unexpected failures in production and unplanned downtime.
Chaos and discipline, These two words are an oxymoron, you might be thinking, how can chaos make disciplined microservices?
But the universal truth is discipline means the absence of chaos, so until you have not experienced chaos you can not be disciplined.
Resilience is something those who use Kubernetes to run apps and microservices in containers aim for. When a system is resilient, it can handle losing a portion of its microservices and components without the entire system becoming inaccessible.
Resilience is achieved by integrating loosely coupled microservices. When a system is resilient, microservices can be updated or taken down without having to bring the entire system down. Scaling becomes easier too, since you don’t have to scale the whole cloud environment at once.