Application Container Architecture for Custom Module Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional development platforms for Java and other programming languages restrict developers to using only pre-shipped modules or module types, limiting flexibility and requiring significant effort to implement customized modules or execution environments.

Innovation Solution

The implementation of an application container architecture that allows for the deployment of applications into new execution environments by using module factories to instantiate and manage modules, enabling the creation and deployment of custom modules and execution environments, and utilizing state machines to track deployment states.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional development platforms use pre-shipped modules only, then system stability is maintained, but adaptability and versatility are limited

Engineering Contradiction:
Improveability to use customized modulesVSAvoidcomplexity of deploying custom modules
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal module deployment framework that allows the same container architecture to handle both pre-shipped modules and custom modules through a common interface. The module container and deployment descriptor mechanism provide multi-functional capability to manage diverse module types without requiring separate deployment processes, thereby improving adaptability while controlling complexity.

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

Solution Approach 2:

The patent segments the deployment system into distinct components: deployment descriptors, module containers, and module factories. This segmentation allows custom modules to be deployed independently through structured descriptors that define module metadata, dependencies, and execution parameters, reducing the complexity of custom module deployment by breaking down the monolithic deployment process into manageable segments.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If developers use custom modules without conventional platform support, then adaptability improves, but implementation effort and complexity increase significantly

Engineering Contradiction:
Improveflexibility in module selectionVSAvoidease of module deployment
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent introduces deployment descriptors as an intermediary layer between custom modules and the execution environment. These descriptors automatically capture module metadata, dependencies, and configuration parameters, serving as a mediator that translates custom module requirements into standardized deployment instructions. This intermediary mechanism enables flexible module selection while maintaining ease of deployment through automated processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The module container architecture implements self-service capabilities by automatically parsing deployment descriptors, resolving dependencies, and configuring module execution environments without requiring manual intervention. The system self-manages the deployment process for custom modules, reducing implementation effort while maintaining flexibility in module selection through automated descriptor-based configuration.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If the system supports multiple module types through extensions, then versatility improves, but device complexity increases

Engineering Contradiction:
Improvesupport for new module typesVSAvoidcomplexity of container architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic module container architecture where the system can adapt to new module types at runtime through extension mechanisms. The container uses reflection and dynamic class loading to instantiate module factories based on deployment descriptor specifications, allowing new module types to be integrated without modifying the core container code. This dynamic approach improves versatility while controlling architecture complexity through runtime adaptability rather than static configuration.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7707572B2System and method for application container architecture
Publication Date: 2010.04.27 ORACLE INT CORP
  • US7707572B2 patent drawing
  • US7707572B2 patent drawing
  • US7707572B2 patent drawing

AI summary

There are provided mechanisms and methods for enabling the deployment of applications into new execution environments by adding extensions to base deployment capability for each of the new containers. These mechanisms and methods can enable embodiments to instantiate modules that augment deployment and/or execution environments for applications being deployed. The ability of embodiments to provide augmented deployment and/or execution environments can enable server embodiments to become more flexible environments from the point of view of developers seeking to implement applications on the server.