Source: azure.microsoft.com
Advancing resilience through chaos engineering and fault injectionCategory: Business, Database, Microsoft, automation
When I first kicked off this Advancing Reliability blog series in my post last July, I highlighted several initiatives underway to keep improving platform availability, as part of our commitment to provide a trusted set of cloud services. Yes, infrastructure is provided in minutes thanks to your public cloud, there are many language options to choose from, swaths of open source code available to leverage, and abundant components and services in the marketplace to build upon.
Fault injection is the deliberate introduction of failure into a system in order to validate its robustness and error handling.
Healthy use of fault injection in a validation process might include one or more of the following: This figure shows a typical release pipeline, and opportunities to include fault injection: An investment in fault injection will be more successful if it is built upon a few foundational components: With these things in place, fault injection can be integrated in the deployment process with little to no additional overhead – and can be used to gate code flow on its way to production.
As Mark Russinovich mentioned in this earlier blog post, our goal is to make native fault injection services available to customers and partners so they can perform the same validation on their own applications and services.
Fault injection is the deliberate introduction of failure into a system in order to validate its robustness and error handling.
Healthy use of fault injection in a validation process might include one or more of the following: This figure shows a typical release pipeline, and opportunities to include fault injection: An investment in fault injection will be more successful if it is built upon a few foundational components: With these things in place, fault injection can be integrated in the deployment process with little to no additional overhead – and can be used to gate code flow on its way to production.
As Mark Russinovich mentioned in this earlier blog post, our goal is to make native fault injection services available to customers and partners so they can perform the same validation on their own applications and services.
Related Articles
Community Partners
DevOps Careers