Encapsulated Application Templates for Containerized Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale network applications with microservice architecture, the management of multiple components and integration of changes is time-consuming and error-prone, requiring manual configuration and verification across multiple services, leading to inefficiencies in bug fixing and QA processes.

Innovation Solution

The development of encapsulated application templates for containerized software, which include identifiers, dependencies, runtime parameters, and configurations, are generated into a transferable platform-independent self-contained machine-readable token, allowing for efficient instantiation and management of containerized applications across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration and verification across multiple services is performed, then application integration and bug fixing can be completed, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improveapplication integration reliabilityVSAvoiddevelopment and QA time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates machine-readable tokens that are copyable representations of application configurations, service dependencies, and runtime parameters. These tokens can be replicated and transferred across devices, eliminating manual reconfiguration and reducing errors while saving time.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent performs preliminary actions by pre-defining service configurations, dependencies, and runtime parameters in the machine-readable tokens before deployment. This advance preparation eliminates the need for manual configuration during integration and testing phases.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the number of components or services in an application increases, then application scalability is improved, but management overhead and integration complexity greatly increase

Engineering Contradiction:
Improveapplication scalabilityVSAvoidmanagement overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the application into independent services with clearly defined machine-readable tokens for each service. This segmentation allows services to be managed independently, reducing management overhead even as the number of services increases, while maintaining scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal machine-readable tokens that can represent any service configuration, dependency, or runtime parameter across different services. This universal format simplifies management by providing a consistent approach to handling diverse service components.

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

3Reliability

If developers and QA engineers manually configure and replace multiple parts of the system to reproduce issues and verify fixes, then bug verification can be performed, but the process creates scenarios where bugs are not reproduced or incorrect configurations are verified

Engineering Contradiction:
Improvebug verification accuracyVSAvoidoperational simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent uses machine-readable tokens as accurate copies of the actual service configurations and dependencies. These tokens ensure that bug reproduction and verification are performed on identical configurations, eliminating discrepancies between development and QA environments.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent implements feedback mechanisms where machine-readable tokens are automatically generated from actual service configurations and fed back to both developers and QA engineers. This ensures both parties work with the same configuration data, improving verification accuracy while maintaining operational simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10579342B1Encapsulated application templates for containerized application software development
Publication Date: 2020.03.03 EMC IP HLDG CO LLC
  • US10579342B1 patent drawing
  • US10579342B1 patent drawing
  • US10579342B1 patent drawing

AI summary

Encapsulated application templates are provided for containerized application software development. An exemplary method for managing a plurality of services in a containerized application program comprises: creating an application template of the containerized application program, the application template comprising an identifier of a current version of each of the plurality of services, dependencies of the given service with other services of the application, runtime parameters and configurations of the given service; generating a transferable platform independent self-contained machine-readable token comprising the application template; and providing the transferable platform independent self-contained machine-readable token comprising the application template to another device as a common entry point to instantiate the containerized application program.