Multi-tenant Workflow Templates for Cloud Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of machine learning and data processing workflows increases significantly in multi-tenant cloud platforms due to the need for separate workflows and jobs for each user and tenant, leading to increased complexity and resource management challenges.
Innovation Solution
Implementing a template-driven approach where pre-defined batch processes (workflow templates) and tenant-specific configurations are used to instantiate and execute tenant-specific batch processes, allowing for common workflows shared across tenants with customizable settings, thereby reducing complexity and improving resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate data process workflows and jobs are created for each tenant and application combination, then tenant-specific customization is achieved, but system complexity increases significantly
Solution Approach 1:
The patent implements a multi-tenant workflow system where a single workflow definition can serve multiple tenants simultaneously. The workflow engine is designed to handle tenant-specific configurations through parameters and variables, allowing the same workflow template to be universally applied across different tenants with customized settings, thereby reducing the need to create separate workflows for each tenant.
Solution Approach 2:
The system uses parameter-driven workflow instantiation where tenant-specific behavior is achieved by changing parameters rather than creating separate workflow definitions. Each tenant can have customized workflow instances by modifying parameters such as tenant ID, data sources, and configuration settings while reusing the core workflow logic, thus maintaining simplicity while enabling customization.
2Reliability
If independent sets of data process workflows are managed for each tenant and application, then tenant isolation is ensured, but resource management becomes more challenging
Solution Approach 1:
The patent merges the management of multiple tenant workflows into a unified workflow engine that handles all tenants through a single system. The engine consolidates workflow definitions, execution control, and resource management while maintaining tenant isolation through logical separation mechanisms such as tenant context and parameter isolation, thereby simplifying resource management while ensuring reliability.
Solution Approach 2:
The workflow engine acts as an intermediary layer between the centralized workflow definitions and individual tenant operations. It manages tenant-specific instances by injecting tenant context and controlling execution parameters, thereby ensuring tenant isolation without requiring separate management systems for each tenant, thus easing resource management.
3Adaptability or versatility
If multiple user multi-tenant systems are supported, then service coverage is expanded, but the complexity of managing workflows across users and tenants increases
Solution Approach 1:
The patent segments the workflow management system into distinct layers: user-level workflow definitions, tenant-level configurations, and execution-level instances. This segmentation allows each layer to be managed independently, reducing the complexity of managing workflows across multiple users and tenants. Each user can define workflows once, and the system automatically segments and instantiates them for each tenant with appropriate configurations.
Data Source
AI summary
Methods, systems, and devices for multi-tenant workflow processing are described. In some cases, a cloud platform may utilize a set of pre-defined batch processes (e.g., workflow templates) and tenant-specific configurations for instantiating and executing tenant-specific batch processes for each tenant of a user. As such, the cloud platform may utilize common data process workflows for each tenant, where a configuration specifies tenant-specific information for the common data process workflows. The workflow templates may include a set of job definitions (e.g., actions for a server to execute) and a schedule defining the frequency for running the templates for a specific project. The configurations may indicate a tenant to execute the workflow templates for, and may include tenant-specific information to override default template information. The cloud platform or a designated server or server cluster may instantiate and execute workflows based on one or more combinations of configurations and indicated workflow templates.