AY WA S A G A M E D AY – H O M I N G L I Dedicated time for teams to collaboratively focus on using Chaos Engineering practices to reveal weaknesses in your services
E D AY S • We were setting hypotheses regarding potential outcomes of our experiments. • We had mapped out our system architecture • Picked specific areas to test, started small, and iterated
• Failure Fridays were a forcing function • I was beginning to uncover brittleness in the UI • I was also beginning to understand our system at a deeper level if ( ) { return }
E E R I N G A N D U I • Graceful degradation currently pertains to browser compatibility or bandwidth. • OSS tooling around failure mitigation in UI is underdeveloped. • Tooling is regularly company specific.
E E R I N G A N D P R O D U C T • Mapping out potential alternative states (reroute, retry) • Product specs that include comprehensive responses to failure scenarios are (anecdotally) rare
O U L D G A M E D AY • Everybody benefits from observing failure • Find your champions across the company • Encourages varied perspectives on failure mitigation