Re-deployable Elastic Framework for Micro-service Governance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing multiple application services struggle with adaptability and resource optimization due to changing technological advancements and policy requirements, necessitating improved frameworks for deployment and resource management.

Innovation Solution

A re-deployable elastic framework structure is introduced, comprising a foundation layer, core layer, and additional layers that support micro-service solutions, allowing for categorization and deployment based on capabilities and data usage, with nodes that can be dynamically reassigned and reconfigured using machine learning for efficient resource sharing and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a rigid framework structure is used for deploying application services, then system stability is maintained, but adaptability to changing technological advancements and policy requirements deteriorates

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

Solution Approach 1:

The framework is divided into multiple hierarchical layers (foundation layer, core layer, service layer, and application layer), allowing each layer to be independently managed and modified. This segmentation enables adaptability changes in upper layers without affecting the stability of lower layers, resolving the contradiction between adaptability and system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The framework introduces dynamic service registration, discovery, and deployment mechanisms that allow services to be added, removed, or modified at runtime without requiring complete system reconfiguration. This dynamic capability enables the system to adapt to changing requirements while maintaining overall framework stability.

Inventive Principle:
Principle #15Dynamics

2Productivity

If manual intervention is used for service deployment and reconfiguration, then deployment control is precise, but deployment time and operational efficiency deteriorate

Engineering Contradiction:
Improvedeployment efficiencyVSAvoiddeployment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The framework implements automated service registration, discovery, and deployment mechanisms where services automatically register themselves with the service registry and can be dynamically discovered and deployed without manual intervention. This self-service capability dramatically improves deployment efficiency while reducing deployment time.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The framework performs preliminary service validation, compatibility checking, and dependency resolution before actual deployment occurs. This preliminary action ensures that services are ready for immediate deployment without requiring manual configuration or troubleshooting during the deployment process, thereby improving deployment efficiency.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If resources are allocated statically to application services, then resource management is simple, but resource utilization efficiency deteriorates

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidresource management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The framework implements dynamic resource allocation where computing resources, storage, and network bandwidth are automatically adjusted based on real-time service performance metrics, workload demands, and priority levels. This dynamic resource management maximizes resource utilization efficiency while the automated nature of the system prevents management complexity from becoming unmanageable.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The framework incorporates continuous monitoring of service performance and resource consumption, using this feedback to automatically adjust resource allocation decisions. This closed-loop feedback mechanism ensures optimal resource utilization while the automated feedback processing prevents management complexity from escalating.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If services are deployed in a monolithic structure, then system architecture is simple, but scalability and flexibility to add new services deteriorate

Engineering Contradiction:
Improveservice scalabilityVSAvoidarchitecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework divides the system architecture into distinct hierarchical layers and independent microservices, allowing individual services to be developed, deployed, and scaled independently. This segmentation enables high scalability and flexibility while the standardized layer interfaces prevent architecture complexity from becoming unmanageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The framework implements universal service interfaces, standardized communication protocols, and common infrastructure components that can be reused across different services and layers. This universality allows new services to be added easily without increasing overall architecture complexity, as they can leverage existing standardized components.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11108654B2Re-deployable elastic framework
Publication Date: 2021.08.31 BANK OF AMERICA CORP
  • US11108654B2 patent drawing
  • US11108654B2 patent drawing
  • US11108654B2 patent drawing

AI summary

The invention relates generally to an improved application structure that allows for layered governance of different or competing functions within a micro application services framework. A segmented layering allows both a horizontal array and a vertical array to build a three dimensional mesh application structure to support multiple services. Each service is supported by base and foundation layers that may be technology agnostic and allow for adaptation according to technological progression or policy evolvement without the need to alter the core micro application services framework. The collection of the framework and supporting layers can be encapsulated into nodes, and a collection of nodes can be grouped into a container hub. Nodes may draw learned behaviors from other nodes, and can isolate themselves when necessary.