Containerized Enterprise Deployment for Rapid Cloud User Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise systems are costly and time-consuming to set up, often requiring months of manual intervention and human supervision, leading to potential system outages and inefficient use of infrastructure due to the need for manual porting of custom applications and services.

Innovation Solution

A cloud-agnostic system using containerization and a platform engine with customizable extensions allows for rapid deployment of enterprise systems in hours, eliminating the need for human supervision and manual review of data and custom applications, utilizing a common processing engine with plug-in applications and data structure extensions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional architecture is used for enterprise system deployment, then system reliability and functionality are ensured, but deployment time and setup cost increase significantly (months vs. hours)

Engineering Contradiction:
Improvesystem functionalityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The enterprise system is divided into independent microservices that can be deployed and scaled separately. Each microservice is encapsulated in its own container, allowing parallel deployment and reducing the overall setup time while maintaining system reliability through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses pre-configured templates and pre-built containers that include all necessary dependencies, configurations, and custom applications. This preliminary preparation eliminates the need for manual setup during deployment, reducing setup time from months to hours while ensuring system functionality is pre-validated.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If manual intervention and human supervision are used for deploying enterprise systems, then configuration accuracy and data import precision are improved, but deployment speed and productivity decrease

Engineering Contradiction:
Improveconfiguration accuracyVSAvoiddeployment speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The deployment system performs self-configuration by automatically extracting data from backup files, validating configurations, and provisioning resources without manual intervention. The system self-verifies configuration accuracy through automated validation checks, eliminating the need for human supervision while maintaining precision and accelerating deployment speed.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the deployment parameters from manual configuration to automated parameter extraction and validation. By using structured data formats and automated configuration generation, the system achieves both high accuracy in configuration and rapid deployment speed through programmable parameter processing.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If a second pre-established enterprise system is maintained for catastrophic events, then system availability and disaster recovery capability are improved, but infrastructure cost and resource utilization increase

Engineering Contradiction:
Improvedisaster recovery capabilityVSAvoidinfrastructure cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Instead of maintaining a complete duplicate enterprise system, the invention creates lightweight containers that replicate only the essential system components and configurations needed for disaster recovery. These containerized copies can be rapidly instantiated from templates, providing disaster recovery capability while significantly reducing infrastructure costs compared to full system duplication.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system discards the need for permanent dual infrastructure by using temporary, on-demand container instances for disaster recovery. When a catastrophic event occurs, the system recovers by rapidly deploying containerized versions of the enterprise system from backup data, eliminating the need for costly permanent duplicate infrastructure while maintaining recovery capability.

Inventive Principle:
Principle #34Discarding and recovering

4Adaptability or versatility

If custom applications and services are manually ported during system deployment, then application functionality and customization are ensured, but deployment complexity and time requirements increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddeployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Custom applications and services are nested within standardized container structures that provide a unified deployment interface. The containerization framework handles the complexity of nesting custom applications, configurations, and dependencies in a hierarchical manner, allowing customization while simplifying the deployment process through standardized container management.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS20250300909A1PROVIDING ACCESS BY A USER TO A NEWLY DEPLOYED ENTERPRISE SYSTEM IN A CLOUD COMPUTING ENVIRONMENT (as amended)
Publication Date: 2025.09.25 FIDELITY INFORMATION SERVICES LLC
  • US20250300909A1 patent drawing
  • US20250300909A1 patent drawing
  • US20250300909A1 patent drawing

AI summary

The present disclosure relates to systems and methods for deploying enterprise systems in cloud environments. In one implementation, a system for deploying an enterprise system in a cloud environment may include at least one processor configured to provide: one or more first containers hosting at least one application with at least one enterprise function; one or more second containers hosting at least one microservice configured to activate the at least one enterprise function; at least one application programming interface (API) between the at least one microservice and at least one client; and at least one gateway configured to manage access to the at least one API.