Orchestration Layer Microservice Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for detecting microservice application failures in communication with an orchestration layer are resource-intensive and time-consuming, often requiring extensive debugging after deployment, which is inefficient in fast-paced development environments.

Innovation Solution

A system and method that validate microservice applications through a first test for availability and a second test for health before deployment, using a mock service application to simulate unavailable systems and allow deployment with failed services, thereby reducing post-deployment debugging time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current failure detection solutions are used, then system reliability is improved, but processing resources and time are excessively consumed

Engineering Contradiction:
Improvefailure detection accuracyVSAvoidprocessing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements pre-deployment validation by performing health checks and connectivity tests on microservice applications before they are deployed to the production environment. This preliminary action detects failures early in the development cycle, ensuring system reliability while avoiding the need for resource-intensive post-deployment debugging and monitoring overhead.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If extensive debugging is performed after deployment, then failure detection accuracy is improved, but time consumption increases significantly

Engineering Contradiction:
Improvefailure detection accuracyVSAvoiddebugging time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs validation tests including health checks and connectivity tests before deployment, moving the debugging action forward in time. This ensures that any failures are detected and resolved during the pre-deployment phase, eliminating the need for time-consuming post-deployment debugging while maintaining high failure detection accuracy.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If pre-deployment validation is implemented, then deployment frequency is improved, but system complexity increases

Engineering Contradiction:
Improvedeployment frequencyVSAvoidvalidation system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The validation system is segmented into distinct, modular components: health check modules that verify application functionality, connectivity test modules that validate service communication, and orchestration layers that coordinate the validation process. This segmentation allows each component to be independently managed and reused, reducing overall system complexity while enabling frequent deployments through automated pre-deployment validation.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11061749B2Systems and methods for failure detection with orchestration layer
Publication Date: 2021.07.13 CAPITAL ONE SERVICES LLC
  • US11061749B2 patent drawing
  • US11061749B2 patent drawing
  • US11061749B2 patent drawing

AI summary

A system and method in accordance with examples may include systems and methods for detecting failure of microservice applications in communication with an orchestration layer of a microservice-architecture. The system may include memory and an orchestration layer including one or more processors coupled to the memory. The one or more processors may be configured to connect the orchestration layer to a plurality of microservice applications that are each associated with a respective dataset. The one or more processors may be configured to validate, responsive to the connection of each of the microservice applications, the microservice applications by performing a first test and a second test. The one or more processors may be configured to deploy, responsive to the validation of the microservice applications, the microservice applications to execute a plurality of workflow actions.