Chaos Testing Prioritization for Critical Deployment Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing chaos testing methods for computer-implemented services expend significant time and resources, impacting the provision of services due to exhaustive testing across all services, without effectively identifying critical failures.
Innovation Solution
Prioritize chaos testing by assigning accessibility weights to services based on their significance to deployment operation, selecting and testing high-weight services to induce failures, and performing diagnostic tests to update the deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If chaos testing is performed on all services exhaustively, then service reliability is improved, but time and resource expenditure increases significantly
Solution Approach 1:
The patent segments the services into critical and non-critical categories based on accessibility weights. Critical services with higher accessibility weights are prioritized for chaos testing, while non-critical services are tested less extensively. This segmentation allows the system to allocate testing resources efficiently, focusing time and computational power on services that have the greatest impact on deployment operation continuity.
Solution Approach 2:
The patent applies local quality by assigning different testing intensities to different services based on their individual accessibility weights. Each service is evaluated and assigned a weight reflecting its criticality, and then tested accordingly - high-weight services receive intensive chaos testing while low-weight services receive minimal or no testing. This localized approach optimizes the balance between reliability improvement and resource consumption.
2Reliability
If chaos testing is performed on all services exhaustively, then service reliability is improved, but resource expenditure increases significantly
Solution Approach 1:
The patent segments services based on accessibility weights to identify which services require intensive resource allocation for testing. By dividing services into critical and non-critical groups, the system can allocate computational resources, testing infrastructure, and human expertise selectively, ensuring adequate resource expenditure on critical services while reducing spending on less critical ones.
Solution Approach 2:
The patent changes the parameter of testing intensity based on accessibility weights. Services with higher accessibility weights are assigned higher testing intensity levels, while services with lower weights are assigned lower intensity levels. This parameter change allows the system to optimize resource expenditure by matching the level of resource allocation to the actual criticality of each service.
3Quantity of substance
If chaos testing is prioritized for high-accessibility services, then resource expenditure is reduced, but testing coverage decreases
Solution Approach 1:
The patent applies local quality by providing differentiated testing coverage matched to the local importance of each service. Critical services with high accessibility weights receive comprehensive chaos testing to ensure thorough coverage, while non-critical services receive reduced testing coverage. This localized differentiation ensures that testing precision is concentrated where it matters most, optimizing the balance between resource expenditure and testing coverage.
Data Source
AI summary
Methods and systems for managing operation of a deployment are disclosed. The deployment may be managed by prioritizing chaos testing of services. The chaos testing may be prioritized by assigning an accessibility weight to a service of the services and selecting the service to perform chaos testing based on the accessibility weight. The accessibility weight may be measure of significance of a service to an ability of the deployment to continue to operate. Services with higher accessibility weights may be selected with which to perform chaos testing. By selecting the services with higher accessibility weights, time and resources of a deployment may not be significantly impacted and may be further allocated to a provision of computer implemented services.


