Cross-Process Dispatch Service for Hybrid Cloud Workloads
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Hybrid cloud deployments face challenges such as data migration and replication between private and public deployments, as well as data security and compliance, particularly when sensitive data and processes need to be shared across these environments.
Innovation Solution
A cross-process dispatch service is implemented in hybrid cloud deployments, which receives work scenario metadata and sensitivity metadata, generates a lineage graph, defines tile segments, and dispatches these segments for execution between private and public cloud systems, ensuring appropriate security and compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data and processes are shared across private and public cloud deployments, then collaboration and functionality are enhanced, but data security and compliance are compromised
Solution Approach 1:
The patent segments the application into multiple deployment contexts (private cloud and public cloud) with distinct runtime environments. Each context maintains its own data and process execution, allowing sensitive operations to remain in the private cloud while non-sensitive operations utilize the public cloud, thus resolving the contradiction between cross-deployment functionality and data security.
Solution Approach 2:
The patent introduces a deployment context runtime as an intermediary layer that manages interactions between private and public cloud deployments. This runtime handles data transfer, process coordination, and security enforcement, enabling secure collaboration across deployment boundaries while maintaining compliance requirements.
2Reliability
If sensitive data and processes are maintained in private deployments, then security and compliance are ensured, but execution throughput and resource utilization are reduced
Solution Approach 1:
The patent divides the workload into segments that can be executed in appropriate deployment contexts. Non-sensitive processes and data are segmented and executed in the public cloud for high throughput, while sensitive operations remain in the private cloud, optimizing both security and productivity.
Solution Approach 2:
The patent applies partial action by allowing only the necessary portions of data and processes to be executed in the public cloud (non-sensitive portions), while keeping sensitive portions in the private cloud. This selective approach maximizes execution throughput for permissible operations without compromising security.
3Adaptability or versatility
If data migration and replication occur between private and public deployments, then functionality and flexibility are improved, but complexity and resource costs increase
Solution Approach 1:
The deployment context runtime acts as an intermediary that manages data migration and replication between private and public deployments. It handles the complexity of data synchronization, format conversion, and transfer coordination, reducing the overall system complexity while maintaining hybrid deployment flexibility.
Solution Approach 2:
The patent creates a universal deployment context runtime that handles multiple functions including data migration, replication, process coordination, and security enforcement across different cloud environments. This multi-functional approach reduces complexity by consolidating multiple operations into a single coordinated system.
Data Source
AI summary
Methods, systems, and computer-readable storage media for receiving, by a cross-process scheduling engine executed within a cloud platform, work scenario metadata and sensitivity metadata, generating, by the cross-process scheduling engine, a lineage graph representing relationships between one or more of data and processes to be executed for a work scenario represented by the work scenario metadata, defining, by the cross-process scheduling engine, a set of tile segments for the work scenario based on the lineage graph and the sensitivity metadata, dispatching, by the cross-process scheduling engine, a first sub-set of tile segments for execution in a private deployment including one or more private nodes, and dispatching, by the cross-process scheduling engine, a second sub-set of tile segments for execution in a public deployment including one or more public nodes.