By proactively introducing chaos, you can identify and address vulnerabilities in your system, building resilience and confidence that it can withstand the unexpected.
It needs to be introduced across the stack where we inject/generate faults -not just in code-, but also operations need to execute their own testing as well for the monitoring/alerting by deliberately causing outages or taking components out of service)
Here's a breakdown of the components to be tested, and the repository issue where technical specifications are documented:
By proactively introducing chaos, you can identify and address vulnerabilities in your system, building resilience and confidence that it can withstand the unexpected.
It needs to be introduced across the stack where we inject/generate faults -not just in code-, but also operations need to execute their own testing as well for the monitoring/alerting by deliberately causing outages or taking components out of service)
Here's a breakdown of the components to be tested, and the repository issue where technical specifications are documented: