Abhishek Vajarekar Sounds like a solid strategy. How do you prioritize which failure scenarios to test, and do you ever have to balance testing depth with the risk of introducing too many disruptions?

Eugene Chernysh We prioritize failure scenarios based on what’s most likely to go wrong and how it could affect the system. For exmaple, we first test things like network lag or databse issues, since those are pretty common. When it comes to balacing how deep we go with testing, we make sure to test in isolated enviroments first, with good monitoring to avoid messing up production. We focus on depth, but always make sure there are recovery steps ready if anything goes wrong.

Nice! Thanks