Process Management Framework for Multi-Protocol Microservice Communication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current process management frameworks are limited in handling multiple transport protocols for microservices communication, lack resume and retry capabilities, and do not provide real-time status tracking or performance analysis.

Innovation Solution

A cloud-based process management framework that enables communication between microservices using different transport protocols, including synchronous and asynchronous protocols, with resume and retry functionalities, and real-time status tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a process management framework supports multiple transport protocols for microservices communication, then the adaptability and versatility of the framework is improved, but the device complexity increases

Engineering Contradiction:

Improvesupport for multiple transport protocolsVSAvoidframework complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component (process management framework) that mediates between microservices and multiple transport protocols. This framework handles protocol selection, routing, and management, allowing microservices to communicate through different protocols without each service needing to implement protocol-specific logic directly, thus managing complexity centrally rather than distributing it across all components

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The process management framework is designed as a universal platform that can handle multiple transport protocols (synchronous, asynchronous, event-driven) through a common architecture. This multi-functional design allows the same framework to manage diverse communication patterns without requiring separate specialized systems for each protocol type

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If the framework implements resume and retry functionalities, then the reliability of microservice communication is improved, but the device complexity increases

Engineering Contradiction:

Improvecommunication reliabilityVSAvoidframework complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The framework performs preliminary actions by pre-configuring retry policies, timeout parameters, and fallback mechanisms before communication failures occur. These parameters are established in advance and automatically applied when failures happen, eliminating the need for complex real-time decision-making logic during failure scenarios

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The framework implements feedback mechanisms that monitor communication status and automatically trigger retry or resume actions based on predefined success criteria. This closed-loop control system continuously monitors message delivery status and adjusts communication attempts accordingly, improving reliability through automated feedback-driven adjustments

Inventive Principle:

Principle #23Feedback

3Measurement precision

If the framework provides real-time status tracking and performance analysis, then the measurement precision is improved, but the use of energy increases

Engineering Contradiction:

Improvestatus tracking precisionVSAvoidcomputing resource consumption

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The framework extracts only the essential status and performance metrics needed for monitoring and analysis, rather than capturing and processing all possible data. This selective extraction approach focuses computational resources on critical parameters (message delivery status, latency, error rates) while ignoring redundant information, reducing overall energy consumption

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11503109B2Processing an operation with a plurality of processing steps

Publication Date: 2022.11.15 CAPITAL ONE SERVICES LLC

AI summary

A device may receive a request for an operation that includes a plurality of processing steps may identify metadata information. The device may determine a first processing step, and select a first microservice to call and a first transport protocol to utilize to call the first microservice. The device may call the first microservice, and may receive, from the first microservice a first output. The device may determine a second processing step, and select a second microservice to call and a second transport protocol to utilize to call the second microservice, wherein the second transport protocol is different from the first transport protocol. The device may call the second microservice, and may receive, from the second microservice, a second output. The device may provide a response to the request based on the first output and the second output.