Cloud Service Initialization Container for Multi-Protocol FaaS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Function-as-a-Service (FaaS) platforms face challenges such as high transformation costs, inadequate multi-language support, high user learning costs, difficulty aligning with internal service governance systems, and limited support for multiple protocols like RPC.
Innovation Solution
The proposed solution involves a cloud service implementation method and apparatus that supports user-defined application mirror images, injects required dependencies using an initialization container, and decouples data and traffic call links to enable multi-protocol support, thereby reducing costs and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If FaaS platforms use standardized runtime environments, then system stability and ease of management are improved, but user learning costs and transformation costs increase
Solution Approach 1:
The patent introduces an initialization container as an intermediary component between the standardized FaaS platform and user applications. This initialization container serves as a mediator that automatically handles the injection of runtime dependencies and configuration files, allowing users to work with standardized environments while the intermediary translates and adapts these standards into application-specific configurations, thereby reducing user learning costs without compromising system stability
2Adaptability or versatility
If FaaS platforms support multiple protocols natively, then adaptability is improved, but system complexity increases
Solution Approach 1:
The patent segments the protocol handling functionality into separate, independent modules within the initialization container. Each protocol (RPC, HTTP, gRPC, etc.) is handled by dedicated configuration files and dependency injection mechanisms, allowing the system to support multiple protocols without creating a monolithic complex structure. This segmentation enables selective activation of protocol handlers based on user needs, maintaining system simplicity while achieving multi-protocol adaptability
3Adaptability or versatility
If FaaS platforms require complete application repackaging, then compatibility is improved, but transformation costs increase
Solution Approach 1:
The patent implements preliminary action by pre-configuring the initialization container with templates for various runtime environments and protocol configurations. These pre-prepared configurations include common dependency files, environment variables, and startup scripts that are ready to be injected into user applications. This preliminary preparation eliminates the need for complete repackaging, as users can simply select from pre-configured templates, thereby maintaining compatibility while significantly reducing transformation costs
4Adaptability or versatility
If FaaS platforms use custom runtime environments, then user flexibility is improved, but cold start time increases
Solution Approach 1:
The patent implements the nested doll principle by embedding the initialization container within the user's application container. The initialization container is a lightweight, self-contained environment that nests essential runtime dependencies and configuration files inside the user's custom runtime environment. This nested structure allows the system to maintain user flexibility for custom runtime configurations while the inner initialization container provides a standardized, pre-configured base that reduces cold start time by avoiding redundant initialization processes
Data Source
AI summary
The present disclosure relates to a cloud service implementation method. The method includes: generating an application instance corresponding to a target service in response to a service request from a client; creating, in the application instance, an initialization container according to a first basic mirror image, starting the initialization container, and writing a binary executable file in the first basic mirror image into a shared directory disc corresponding to the application instance; creating, in the application instance, an application container based on an application mirror image, reading the binary executable file from the shared directory disc, and injecting the binary executable file into the application container; running the binary executable file in the application container, to start a RuntimeAgent process; and calling the RuntimeAgent process to control a runtime process in the application instance to execute a file in the application mirror image, to process the service request.