Microservice Validator for Deployment Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Microservices deployments often result in system instability and performance issues due to incompatible combinations of components or version differences, requiring significant user involvement and costly reconfigurations to optimize the user environment.

Innovation Solution

A multi-phase microservice validator process that tests application catalogs in pilot environments, calculates similarities with the user's environment, and selects optimal application templates for deployment, ensuring compatibility and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If microservices are deployed without prior validation, then deployment speed is improved, but system stability and performance deteriorate due to incompatible component combinations

Engineering Contradiction:
Improvedeployment speedVSAvoidsystem stability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements a multi-phase validation process that performs compatibility testing, fault injection, and performance evaluation before microservice deployment. This preliminary action identifies incompatible component combinations and resolves conflicts in advance, ensuring system stability is maintained while preserving rapid deployment capabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The validation system automatically tests microservice combinations, detects faults, and performs self-healing operations without requiring manual user intervention. This automated self-service approach maintains deployment speed by eliminating manual testing and configuration steps while ensuring system reliability through comprehensive pre-deployment validation.

Inventive Principle:
Principle #25Self-service

2Reliability

If comprehensive validation testing is performed before deployment, then system reliability is improved, but deployment time and complexity increase

Engineering Contradiction:
Improvesystem stabilityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The validation process is divided into distinct phases including compatibility testing, fault injection, and performance evaluation. Each phase focuses on specific aspects of system reliability, allowing comprehensive validation to be performed systematically without overwhelming deployment time. The segmented approach enables parallel processing and optimization of individual testing stages.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts validation parameters such as testing depth, fault injection intensity, and performance thresholds based on the specific microservice combination being deployed. This adaptive parameter adjustment ensures comprehensive reliability validation while minimizing unnecessary testing overhead and reducing overall deployment time.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If manual user involvement is used for testing and configuration, then system adaptability is improved, but operational complexity and cost increase

Engineering Contradiction:
Improveenvironment compatibilityVSAvoidoperational complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The validation system automatically adapts to different user environments by performing compatibility testing, detecting environmental characteristics, and configuring optimal microservice combinations without manual user involvement. This self-service capability maintains high system adaptability while eliminating the operational complexity and costs associated with manual testing and configuration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors validation results and environmental feedback to automatically adjust configurations and select optimal microservice combinations. This feedback-driven approach enables the system to adapt to diverse user environments autonomously, maintaining versatility while reducing operational complexity through automated decision-making based on real-time performance data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10635572B2System and method for microservice validator
Publication Date: 2020.04.28 HITACHI VANTARA LTD
  • US10635572B2 patent drawing
  • US10635572B2 patent drawing
  • US10635572B2 patent drawing

AI summary

Example implementations described herein are directed to systems and methods for validating and deploying microservices. In an example implementation, a plurality of similarities are calculated between a user environment and multiple pilot environments from application deployment test results. The test results are based on compatibility of catalogs of applications with each of the pilot environments. A list is presented with one or more of the catalogs of applications that are indicated as compatible and similar to the user environment based on the calculated similarities. The user can select catalog from the list that is deployed in the user environment.