Container Deployment Module for PaaS Function Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current PaaS solutions with monolithic architectures face challenges in migrating applications, setting up hybrid platforms, extending functionality, debugging, and providing portability and service discovery, especially when shifting to microservices architectures, which increases complexity and responsibility for developers.
Innovation Solution
A deployment module that manages containers by associating them with additional functions such as service discovery, self-healing, and scaling, allowing seamless execution on various platforms without requiring developers to be aware of these mechanisms, using a list of functions that are automatically injected into the container during deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a monolithic architecture is used for PaaS platforms, then the platform provides integrated management and core functions, but it becomes difficult to migrate applications, setup hybrid platforms, extend functionality, and debug applications
Solution Approach 1:
The patent segments the PaaS platform into independent components: container runtime environment, deployment module, and platform functions. This segmentation allows the platform to be migrated, extended, and debugged by manipulating individual components rather than the entire monolithic system, directly resolving the technical contradiction between platform flexibility and architecture complexity.
Solution Approach 2:
The patent extracts the container runtime environment from the PaaS platform, allowing it to be independently deployed and managed. This extraction enables application migration and platform extension without being constrained by a monolithic architecture, thereby improving platform flexibility while reducing architectural complexity.
2Adaptability or versatility
If containers are used to build applications on PaaS platforms, then portability and flexibility are improved, but additional adaptation is required for each platform to use scaling and resilience functions
Solution Approach 1:
The patent implements a universal deployment module that handles platform-specific adaptations for scaling and resilience functions. This module provides multi-functionality by supporting multiple PaaS platforms (Kubernetes, Mesos, YARN) through a single standardized interface, allowing containers to maintain portability while automatically accessing platform-specific features without requiring application-level adaptation.
Solution Approach 2:
The deployment module acts as an intermediary between containers and PaaS platforms. It translates container deployment requests into platform-specific configurations for scaling and resilience, eliminating the need for containers to directly adapt to each platform's proprietary mechanisms while maintaining full functionality.
3Productivity
If microservices architecture is adopted, then complex applications can be broken into small independent processes, but developer responsibility and system complexity increase
Solution Approach 1:
The patent implements self-service mechanisms where the deployment module automatically discovers, deploys, and manages microservices. The system performs self-configuration, health monitoring, and scaling without requiring developers to manually manage each microservice's lifecycle, thereby maintaining high development efficiency while reducing the operational complexity burden on developers.
Solution Approach 2:
The patent incorporates feedback mechanisms through automated monitoring and health checking of microservices. The deployment module continuously receives feedback from running microservices and automatically adjusts resource allocation, scaling, and recovery actions, reducing system complexity by replacing manual developer intervention with automated closed-loop control.
Data Source
AI summary
A method and a deployment module (110) for managing a container to be deployed on a software platform (120) are disclosed. The container provides a first set of functions. The deployment module (110) obtains (203) the container. The deployment module (110) obtains (204) a list specifying a second set of functions for the container. The deployment module (110) associates (205) the container, based on the list, with the second set of functions. The container, when deployed, provides the first and second set of functions when executed on the software platform (120). A corresponding computer program and a carrier therefor are also disclosed.