Microservice Deployment Metadata Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current orchestration environments in cloud computing do not adequately consider communication relationships, resource needs, and security requirements when deploying microservices, leading to inefficiencies in network overhead, resource utilization, and security overhead.
Innovation Solution
The proposed solution involves extending metadata associated with microservices to include communication relationships, resource needs, and security requirements, allowing the orchestration framework to make informed decisions about node placement, resource allocation, and security configurations, such as using shared memory for communication and optimizing node-level resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If microservices are deployed using traditional orchestration environments, then deployment can be achieved, but network overhead increases due to lack of communication relationship optimization
Solution Approach 1:
The patent applies preliminary action by pre-defining communication relationships, resource needs, and security requirements in metadata before deployment. The orchestration framework uses this pre-prepared information to make informed placement decisions, avoiding the need for complex runtime optimization and reducing network overhead from the start.
Solution Approach 2:
The patent introduces metadata as an intermediary layer between microservices and the orchestration framework. This metadata structure acts as a mediator that carries communication relationship information, resource requirements, and security preferences, enabling the orchestrator to make optimized decisions without direct complex interactions between components.
2Productivity
If microservices are deployed without considering resource needs, then deployment is simplified, but resource utilization becomes suboptimal
Solution Approach 1:
The patent applies preliminary action by requiring resource needs to be specified in metadata before deployment. This allows the orchestration framework to pre-plan resource allocation and node placement, ensuring optimal resource utilization without adding complex runtime resource management mechanisms.
Solution Approach 2:
The patent changes the parameter representation by extending metadata to include structured resource requirement information. This allows the orchestration system to work with explicit resource parameters (CPU, memory, storage, network) rather than relying on default or estimated values, improving resource utilization through informed decision-making.
3Reliability
If traditional deployment methods are used, then deployment process is simple, but security requirements are not adequately addressed
Solution Approach 1:
The patent applies preliminary action by incorporating security requirements into metadata before deployment. This allows security configurations to be determined upfront based on service characteristics and communication relationships, ensuring adequate security without adding complex runtime security management.
Solution Approach 2:
The patent changes the deployment parameters by extending metadata to include security-related information such as security levels, authentication requirements, and encryption needs. This enables the orchestration framework to make security-informed placement and configuration decisions as part of the standard deployment process.
4Loss of energy
If microservices are deployed without considering communication relationships, then deployment is faster, but network overhead increases
Solution Approach 1:
The patent applies preliminary action by pre-defining communication relationships in metadata, enabling the orchestration framework to make informed placement decisions during deployment. This upfront preparation allows the system to optimize network communication patterns without requiring iterative adjustments after deployment.
Solution Approach 2:
The patent uses metadata as an intermediary that carries communication relationship information between microservices and the orchestration framework. This structured intermediate representation enables efficient processing of communication patterns during deployment, reducing network overhead while maintaining reasonable deployment speeds.
Data Source
Figure 1
Figure 2A~2B
Figure 3
AI summary
In one embodiment, metadata associated with deployment of a container within an orchestration environment includes information indicating security preferences for deployment of the container within the orchestration environment, information indicating a level of communications between the container and other containers, and/or information indicating effects of execution of the container with respect to other containers. The metadata is used to select a particular node of a plurality of nodes within the orchestration environment on which to deploy the container based on the metadata.