Chaos Engineering has appeared as a very useful practice for increasing application resiliency. However, most teams start using Chaos Engineering only after incidents happened and after a lot of pain in dealing with the reliability issues. Is it possible to have a proactive reliability practice, a shift-left in this domain, similar to what TDD is doing for testing and design?
This is the key question in this open conversation with Nils Wloka. Nils Wloka is Vice President Engineering at steadybit, a former coach and very interested in reliability and resilience of applications. For his work, he has done research related to reliability practices, and we explore together the root causes for avoiding their use and find practices that might help you increase your product’s resilience.
- steadybit https://steadybit.com. Try it out for free at https://signup.steadybit.com/
- The steadybit YouTube channel https://www.youtube.com/@steadybit
- Find Nils on Twitter https://twitter.com/nilswloka or LinkedIn https://www.linkedin.com/in/nilswloka/
- The toot that started the conversation https://mastodon.nilswloka.com/@nils/109298571937715047