Brokered Serverless Database Provisioning Across Multi-Cloud Private Clouds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customers subscribing to a cloud environment are restricted to using services offered by that cloud environment and lack an easy way to access services from different cloud service providers, limiting flexibility and interoperability.

Innovation Solution

A method for provisioning and managing serverless database resources across multiple cloud environments involves identifying resource locations, creating network links, and generating metadata to enable data flow between private clouds, with mechanisms for failover and resource allocation using a broker to manage multi-cloud IDs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a customer subscribes to a cloud environment provided by a CSP, then the customer can use the services offered by that cloud environment, but the customer is restricted to using only those services and cannot easily access services from different CSPs

Engineering Contradiction:
Improvecross-cloud service accessVSAvoidmulti-cloud provisioning complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a broker cloud environment that acts as an intermediary between customers and multiple CSP cloud environments. The broker receives service requests from customers, translates them into appropriate CSP-specific requests, and manages the provisioning process across different cloud providers. This intermediary layer enables cross-cloud service access without requiring customers to directly interact with multiple complex cloud ecosystems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The broker cloud environment provides universal access to services from multiple CSPs through a single interface. It implements multi-functionality by supporting various cloud service types (IaaS, PaaS, SaaS) from different providers, managing resource provisioning, and handling failover scenarios across heterogeneous cloud environments through a unified system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If cloud services are provisioned across multiple private clouds, then data can flow between different private clouds enhancing flexibility, but the system complexity and management overhead increase

Engineering Contradiction:
Improvedata flow between private cloudsVSAvoidmulti-cloud infrastructure management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The broker cloud environment serves as a mediator that manages data flow and communication between multiple private clouds. It handles the complexity of inter-cloud networking, security policies, and resource coordination, allowing data to flow seamlessly between private clouds while the broker absorbs the management overhead and system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments cloud infrastructure management into distinct functional layers: the broker layer handles high-level service provisioning, resource allocation, and cross-cloud coordination, while individual CSP layers handle their own infrastructure management. This segmentation allows data flow between private clouds while distributing management complexity across specialized components.

Inventive Principle:
Principle #1Segmentation

3Reliability

If failover mechanisms are implemented across multiple cloud locations, then service reliability is improved, but the provisioning and management complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidfailover management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The broker cloud environment acts as an intermediary that manages failover mechanisms across multiple cloud locations. It monitors service health, detects failures, and automatically redirects workloads to healthy cloud instances. This centralizes failover management in the broker layer, improving service reliability while preventing complexity from propagating to individual cloud provisioning processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-configuring failover policies, resource mappings, and recovery procedures in the broker environment before failures occur. Service definitions, resource templates, and failover rules are established in advance, enabling automatic response to failures without requiring complex real-time decision-making during actual failure events.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250267201A1Provisioning and managing serverless database resources within a multi-cloud infrastructure
Publication Date: 2025.08.21 ORACLE INT CORP
  • US20250267201A1 patent drawing
  • US20250267201A1 patent drawing
  • US20250267201A1 patent drawing

AI summary

Techniques described herein include receiving, by a first cloud environment and from a second cloud environment, a request to provision a cloud service from among a plurality of cloud services provided by a cloud service provider associated with the first cloud environment. The techniques further include, performing a set of operations associated with provisioning the cloud service in the second cloud environment, wherein at least one operation of the set of operations comprises identifying one or more resource locations of a plurality of private clouds of the first cloud environment for executing the cloud service. The techniques further include, provisioning the cloud service in the plurality of private clouds, wherein the provisioning enables data pertaining to the cloud service to flow between a resource location of a first private cloud and a resource location of one or more second private clouds of the plurality of private clouds.