Bayesian Defect Prediction for Cloud Microservices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Microservice-based applications in cloud infrastructures face challenges in modeling and predicting defects, as well as securing against attacks, due to their complex and distributed nature, which traditional architectures cannot effectively address.

Innovation Solution

The implementation uses an additive Weibull distribution for network traffic modeling to predict resource needs and a Bayesian statistical framework to identify defective microservices, along with real-time monitoring and classification of network packets to detect security threats, enabling proactive resource scaling and threat mitigation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If microservice-based applications are deployed in cloud infrastructures to provide scalable and flexible computing resources, then adaptability and productivity are improved, but device complexity and difficulty of detecting and measuring defects increase

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the complex microservice system into individual observable characteristics and defect types. Each microservice is analyzed independently for specific characteristics (e.g., response time, error rates) and defect types (e.g., memory leaks, network issues), making the complex system manageable through modular analysis units that can be processed separately and aggregated.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces Bayesian statistical models as intermediary tools that mediate between raw observability data and defect predictions. The Bayesian framework acts as a mediator that processes complex multi-service interactions and propagates defect probabilities through the microservice architecture, enabling indirect observation of defects in distributed systems where direct measurement is difficult.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If traditional architectures with monolithic applications are used, then ease of operation and ease of detecting and measuring defects are improved, but adaptability and productivity deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidadaptability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent replaces manual defect detection methods (mechanical approaches) with automated Bayesian statistical analysis. Instead of relying on traditional monitoring tools that work well for monolithic applications, the system uses probabilistic models that automatically analyze service-level observability data, substituting automated statistical inference for manual or rule-based defect detection approaches.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent changes the fundamental parameters of defect detection by shifting from direct observation of application internals (effective in monolithic systems) to indirect observation through service-level metrics and Bayesian probability calculations. This parameter transformation enables defect detection in distributed microservice architectures where traditional direct measurement parameters are no longer accessible.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If microservices are deployed and used by many different users to meet demand, then productivity is improved, but object-affected harmful factors increase due to security risks and attacks

Engineering Contradiction:
ImproveproductivityVSAvoidsecurity risks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by using Bayesian models to predict potential defects and security issues before they manifest as actual failures. The system continuously calculates defect probabilities based on current observability data, enabling proactive identification of vulnerable microservices before malicious users can exploit them, thus preventing security incidents rather than merely responding to them.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements continuous feedback loops where observability data from microservice operations is constantly fed into Bayesian models, which update defect probabilities in real-time. This feedback mechanism allows the system to learn from ongoing service interactions and adjust security postures dynamically, identifying patterns that indicate potential security threats before they escalate into harmful attacks.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10528450B2Predicting defects in software systems hosted in cloud infrastructures
Publication Date: 2020.01.07 SAP SE
  • US10528450B2 patent drawing
  • US10528450B2 patent drawing
  • US10528450B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for detecting a source of a defect in microservice-based applications, implementations including receiving at least one error log, the at least one error log including event data associated with at least one microservice in a set of microservices hosted on a cloud infrastructure, determining, for each microservice in the set of microservices, and for each type of defect in a set of types of defects, a probability that a respective microservice has a respective type of defect, and executing at least one action based on a probability indicating that a microservice of the set of microservices has a type of defect.