Request Forwarder for Multi-Cloud Job Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud services like AWS EKS and ECS lack a built-in orchestration component to manage jobs that run sequentially, making it difficult to initiate and handle errors within batch architectures.
Innovation Solution
A method for multi-cloud task orchestration is introduced, where a workflow task function creates jobs for a container orchestration system, forwards them as serverless tasks using a request forwarder, waits for job status, and continues with subsequent jobs, leveraging serverless functions like Lambda and integrating with Kubernetes and Active Directory Federation Services for secure and compliant execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a workflow task function creates jobs for a container orchestration system, then job orchestration capability is improved, but the system complexity increases due to the inability to call services directly
Solution Approach 1:
The patent introduces a request forwarder as an intermediary component that sits between the workflow task function and the container orchestration system. This forwarder receives job creation requests from the workflow function, forwards them to the appropriate Kubernetes API endpoints, and returns job status information. This intermediary pattern resolves the contradiction by enabling orchestration capability while managing system complexity through a dedicated mediation layer that handles the complexity of direct service calls.
2Reliability
If direct service calls are blocked for security reasons, then security is improved, but the ability to initiate and monitor jobs deteriorates
Solution Approach 1:
The request forwarder acts as a secure intermediary that enables job initiation and monitoring without requiring direct service calls from the workflow function. It receives authenticated requests, forwards them to Kubernetes APIs with appropriate credentials, and returns job status information. This maintains security by blocking direct unauthorized access while preserving operational capability through the trusted intermediary layer.
Solution Approach 2:
The system segments the job management functionality into separate components: the workflow task function that defines job logic, the request forwarder that handles communication, and the Kubernetes cluster that executes jobs. This segmentation allows each component to have specific security permissions, improving overall security while maintaining ease of operation through clear separation of concerns.
3Adaptability or versatility
If multiple cloud platforms are supported, then adaptability is improved, but integration complexity increases
Solution Approach 1:
The request forwarder is designed as a universal component that can interface with multiple cloud platforms and container orchestration systems through standardized Kubernetes APIs. Rather than implementing separate integration logic for each cloud provider, the forwarder uses a single unified approach that works across AWS EKS, Azure AKS, Google GKE, and on-premises Kubernetes deployments, thereby achieving multi-cloud support without proportionally increasing integration complexity.
Data Source
AI summary
Systems and methods for multi cloud task orchestration are disclosed. In one embodiment, a method for multi cloud task orchestration may include: (1) creating, by a workflow task function, a first job for a service provided on a container orchestration system, wherein the workflow task function cannot call the service directly; (2) forwarding, by the workflow task function, the first job to the service as a serverless task/function using a request forwarder; (3) waiting, by the workflow task function, for a period of time; (4) checking, by the workflow task function, a status of the first job with the serverless task/function, (5) receiving, by the workflow task function, the status of the first job; and (6) continuing, by the workflow task function, with a second job for the service provided on the container orchestration system.