Cloud-Native Integration Server Migration With Minimal Downtime

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Upgrading cloud services from a single tenant to a multi-tenant environment often results in significant downtime, disrupting user access and negatively impacting the user experience.

Innovation Solution

A method involving an eligibility status check, data export to a common storage, provisioning of a new cloud service instance, data import, and activating the new instance while redirecting user access, utilizing directed acyclic graphs (DAGs) to manage the upgrade process, ensuring minimal downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud services are upgraded from single tenant to multi-tenant environment, then cloud service version and environment capability are improved, but service downtime and user access disruption increase

Engineering Contradiction:

Improvecloud service versionVSAvoidservice downtime

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating a preview environment before the actual upgrade. The system creates a preview multi-tenant cloud service instance, copies data to it, and performs eligibility checks in advance. This allows the upgrade process to be tested and validated before switching user access, thereby minimizing actual downtime during the production upgrade.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent segments the upgrade process into distinct phases: creating a preview environment, copying data, performing eligibility checks, and finally switching user access. This segmentation allows each phase to be executed and validated independently, reducing the risk and duration of service disruption during the actual upgrade.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If cloud services are upgraded from single tenant to multi-tenant environment, then cloud service version and environment capability are improved, but user access disruption and experience degradation increase

Engineering Contradiction:

Improvecloud service versionVSAvoiduser access

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary mechanism by creating a preview environment that acts as a buffer between the old single-tenant service and the new multi-tenant service. Users can be redirected to the preview environment during the transition, ensuring continuous access without direct disruption from the upgrade process itself.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

By performing the upgrade in a preview environment first, the system validates compatibility and functionality before making it live. This preliminary validation ensures that when users are redirected to the upgraded service, access disruptions are minimized and the transition is seamless.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If data is exported and imported during upgrade process, then environment transition from single to multi-tenant is achieved, but processing time and upgrade duration increase

Engineering Contradiction:

Improveenvironment transitionVSAvoidupgrade duration

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs data export and eligibility checks in advance during the preview environment creation phase. By copying data to the preview environment and validating eligibility before the actual upgrade, the system reduces the time required during the production upgrade, as data preparation is already completed.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous useful action by allowing the original cloud service to continue operating while the preview environment is being prepared. Data copying and eligibility checks occur in the background without interrupting the original service, ensuring that the upgrade process does not create idle time or stoppages.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS12436757B2Onboarding of customers from single tenant to multi-tenant cloud-native integration server

Publication Date: 2025.10.07 ORACLE INT CORP

AI summary

Techniques are disclosed herein for onboarding users from a single tenant cloud environment to a multi-tenant cloud environment. In one aspect, a method is provided that includes in response to an eligibility status check indicating that a first cloud service instance running a first version of a cloud service in a first cloud environment is eligible for the upgrade, exporting a copy of data from the first cloud service instance to a common storage device, provisioning a second cloud service instance running on the second version of the cloud service in a second cloud environment, importing the first copy of the data from the common storage device to the second cloud service instance, and activating the second cloud service instance to run the second version of the cloud service. During the exporting, provisioning, and importing the first cloud service instance continues to run the first version of the cloud service.