Data Isolation for Lifecycle Phase Resource Optimization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In cloud services, it is challenging to determine whether a message or output is from a production or test aspect of an application, leading to confusion and increased costs due to the instability and error-prone nature of developing applications, as well as the expense of providing separate resources for testing and production environments.

Innovation Solution

Implementing data isolation for lifecycle phases of an application, where test and production data isolations are created, allowing only specific access to process definitions, authorization, credentials, or runtime data based on the selected lifecycle phase, enabling a unified login procedure across phases without the need for multiple systems or resource topologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate resources are provided for testing and production environments, then reliability is improved, but device complexity and cost increase

Engineering Contradiction:

Improveapplication stabilityVSAvoidresource topology

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data access by creating distinct data isolations for different lifecycle phases (test, production). Each phase has its own isolated data space, preventing interference between test and production applications while sharing the same underlying resource infrastructure. This resolves the contradiction by providing logical separation without physical duplication.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (data isolation mechanism) between the application and the shared resource. This intermediary controls and manages access to resources based on lifecycle phase, enabling multiple applications to share resources safely while maintaining their independence and reliability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If separate resources are provided for testing and production environments, then reliability is improved, but cost increases

Engineering Contradiction:

Improveapplication stabilityVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges the test and production environments by allowing them to share the same resource infrastructure. Through data isolation, multiple lifecycle phases can coexist on the same physical resources, reducing the quantity of resources needed while maintaining the reliability benefits of separation.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent makes resources universal by enabling a single resource to serve multiple lifecycle phases simultaneously. The resource infrastructure becomes multi-functional, supporting both test and production applications through the data isolation mechanism, thereby reducing overall resource consumption.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If test and production data are mixed, then resource usage is optimized, but measurement precision deteriorates

Engineering Contradiction:

Improveresource utilizationVSAvoiddata source identification

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The patent segments the data space into distinct isolations for different lifecycle phases. This segmentation allows precise identification of data sources (test vs. production) while enabling efficient resource utilization, as the same physical resources can be used for both purposes without data contamination.

Inventive Principle:

Principle #1Segmentation

4Reliability

If multiple systems are used for different lifecycle phases, then reliability is improved, but device complexity increases

Engineering Contradiction:

Improvelifecycle phase isolationVSAvoidsystem architecture

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data isolation intermediary that sits between the application and the resource layer. This intermediary provides the necessary isolation for different lifecycle phases without requiring separate physical systems, thereby maintaining reliability while simplifying the overall system architecture.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10552591B2Resource optimization using data isolation to provide sand box capability

Publication Date: 2020.02.04 ORACLE INT CORP

AI summary

According to one embodiment, data isolation is provided with respect to lifecycle phases of an application. For example, a test data isolation and a production data isolation of at least one resource are created. The test data isolation corresponds with a test lifecycle phase of the application and the production data isolation corresponds with a production lifecycle phase of the application. A first set of data is stored in the test data isolation and a second set of data is stored in the production data isolation. A test version of the application is executed in the test data isolation. A production version of the application is executed in the production data isolation. A particular executing version of the application is allowed to only access data according to a lifecycle phase selected for a user.