Orchestration Engine Builder Automates Dependency Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing product orchestration engines requires cross-domain knowledge and expertise, making it complex for developers to specify dependencies and leverage services from other product orchestration engines, and existing techniques do not adequately simplify this process.
Innovation Solution
An intelligent product orchestration engine builder that automates dependency resolution, resource requirements declaration, and tooling installation, allowing developers to focus on product domain knowledge, using a REST interface and JSON formatted files to simplify the development process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers manually specify dependencies and configure product orchestration engines, then the system can leverage services from other product orchestration engines, but the development process becomes complex and requires cross-domain knowledge
Solution Approach 1:
The system performs automated dependency resolution where the product orchestration engine automatically determines and configures dependencies on other services without requiring manual developer intervention. The engine self-services by resolving dependencies, installing required tooling, and configuring resource requirements automatically based on service catalogs and metadata.
Solution Approach 2:
A service catalog acts as an intermediary between developers and the complex dependency resolution process. The catalog stores metadata about available services and their dependencies, allowing the engine to automatically resolve dependencies without developers needing cross-domain knowledge of other orchestration services.
2Reliability
If developers manually configure resource requirements and install tooling, then the product orchestration engine can be properly set up, but the development process requires significant cross-domain knowledge and effort
Solution Approach 1:
The system performs preliminary actions by automatically determining resource requirements and installing necessary tooling before the product orchestration engine needs to run. The engine proactively configures dependencies, installs dependencies, and sets up the development environment in advance, eliminating the need for developers to manually perform these complex tasks.
Solution Approach 2:
The product orchestration engine automatically self-configures by determining its own resource requirements and installing its own tooling dependencies without developer intervention. The engine queries service catalogs, resolves dependencies, and automatically provisions the necessary environment.
3Ease of operation
If the system automates dependency resolution and tooling installation, then the development process is simplified and requires less cross-domain knowledge, but additional automation infrastructure is needed
Solution Approach 1:
The service catalog system serves multiple functions: it stores service metadata, resolves dependencies, manages resource requirements, and tracks tooling installations. This multi-functional approach consolidates what would otherwise require separate systems into a single universal platform, reducing overall infrastructure complexity while maintaining automation capabilities.
Data Source
AI summary
A system can receive information about a first orchestration service that indicates a mapping from an application programming interface (API) to an executable script, and a dependency of the first orchestration service on a second orchestration service. The system can, in response to receiving the information, creating a base container image for the first orchestration service. The system can associate the API with executing the executable script on the base container image. The system can associate the dependency of the first orchestration service on the second orchestration service with the base container image. The system can, in response to receiving data indicative of a request to create an instance of the first orchestration service, creating an instance of the base container image.