Orchestrator System for Multi-Cloud Service Composition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing environments lack flexibility in deploying applications across different cloud services, as each application has unique requirements that may not be met by a single cloud environment, leading to inefficient operation and function of distributed applications.
Innovation Solution
The orchestrator system models distributed applications using abstract elements and functional models, dynamically selects and instantiates cloud services, and manages resources to deploy applications across multiple cloud environments, including private, public, and server-less infrastructures, allowing for dynamic creation of cloud services if needed, and managing them as applications themselves.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If applications are deployed on a single cloud environment with fixed service configurations, then deployment simplicity is maintained, but application efficiency and adaptability deteriorate due to inability to meet diverse functional requirements
Solution Approach 1:
The patent creates a universal cloud service architecture where services can function both as standalone components and as composable building blocks. The service registry and orchestrator enable a single service to be discovered and utilized by multiple applications in different configurations, achieving multi-functionality without requiring separate specialized services for each application scenario.
Solution Approach 2:
The patent implements a nested service architecture where cloud services can be composed hierarchically - basic services form the foundation, intermediate services build upon them, and application-specific services nest multiple lower-level services together. This allows complex application requirements to be met by nesting simpler services, reducing overall system complexity while maintaining adaptability.
2Productivity
If cloud services are dynamically created and composed to meet application requirements, then service adaptability improves, but system complexity and orchestration difficulty increase
Solution Approach 1:
The patent pre-registers service templates and defines service interfaces, dependencies, and composition rules before actual application deployment. The orchestrator has access to pre-validated service catalogs and composition patterns, allowing it to rapidly assemble services without performing complex real-time analysis, thus improving deployment efficiency while keeping orchestration manageable.
Solution Approach 2:
The patent introduces an orchestrator as an intermediary layer between application requirements and cloud services. The orchestrator translates high-level application needs into service composition plans by querying the service registry and applying pre-defined composition rules, thereby shielding applications from orchestration complexity while enabling efficient service assembly.
3Reliability
If applications are distributed across multiple cloud environments, then operational efficiency improves, but deployment complexity and resource management difficulty worsen
Solution Approach 1:
The patent creates a universal service registry that can discover and manage services across multiple cloud environments through a common interface. Applications interact with a single orchestrator that handles multi-cloud service composition, providing universal access to diverse cloud resources without requiring application-specific multi-cloud management logic.
Solution Approach 2:
The orchestrator serves as an intermediary that abstracts multi-cloud complexity from applications. It manages service discovery, composition, and deployment across multiple cloud environments using unified service templates and composition rules, thereby improving application reliability through diverse cloud deployment while keeping management complexity centralized and manageable.
Data Source
AI summary
The present disclosure involves systems and methods for (a) model distributed applications for multi-cloud deployments, (b) derive, by way of policy, executable orchestrator descriptors, (c) model underlying (cloud) services (private, public, server-less and virtual-private) as distributed applications themselves, (d) dynamically create such cloud services if these are unavailable for the distributed application, (e) manage those resources equivalent to the way distributed applications are managed; and (f) present how these techniques are stackable. As applications may be built on top of cloud services, which themselves can be built on top of other cloud services (e.g., virtual private clouds on public cloud, etc.) even cloud services themselves may be considered applications in their own right, thus supporting putting cloud services on top of other cloud services.