Hybrid Cloud Workflow Execution via Event Queue Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud architectures face challenges in seamlessly executing and managing workflows across hybrid cloud environments, particularly in ensuring secure and efficient communication and execution of tasks between private and public data centers with restricted network access.

Innovation Solution

The implementation of a hybrid cloud system that includes a private data center and a cloud data center, where an event queue is used to publish events, and an event handler in the private data center executes workflows, publishing results back to the cloud data center, facilitating seamless execution and tracking of workflows while maintaining network security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a private data center implements restricted network access to maintain security, then security and trust relationships are improved, but workflow execution and communication with cloud services deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidworkflow execution
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

An event queue is introduced as an intermediary component between the private data center and cloud services. The event queue receives events from cloud services and delivers them to event handlers in the private data center, enabling workflow execution without requiring direct network access. This mediator allows secure isolated execution while maintaining communication capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If cloud services are accessed directly from a private data center, then workflow execution capability is improved, but network security and trust relationships deteriorate

Engineering Contradiction:
Improveworkflow executionVSAvoidnetwork security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system is segmented into distinct components: cloud services in the public cloud, an event queue as a communication interface, and event handlers in the private data center. This segmentation allows workflow execution capabilities to be introduced through the event queue without compromising the security boundary of the private data center network.

Inventive Principle:
Principle #1Segmentation

3Reliability

If an event queue is introduced to enable secure workflow execution, then network security is improved, but system complexity increases

Engineering Contradiction:
Improvenetwork securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The event queue operates autonomously, managing event storage, retrieval, and delivery without requiring complex configuration or management infrastructure. Event handlers simply consume events from the queue and execute workflows, making the system self-sufficient and reducing operational complexity despite the added security layer.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10887283B2Secure execution and tracking of workflows in a private data center by components in the cloud
Publication Date: 2021.01.05 VMWARE INC
  • US10887283B2 patent drawing
  • US10887283B2 patent drawing
  • US10887283B2 patent drawing

AI summary

One or more embodiments provide techniques for executing a workflow in a private data center. The cloud data center receives a request from a user. The cloud data center publishes an event to an event queue in the cloud data center. An event handler in the private data center accesses the event queue. The event handler executes the workflow in response to the event in the private data center. The event handler publishes the results of the workflow in the cloud data center.