Declarative Data Evacuation for Cloud Database Pods

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing platforms face challenges in efficiently and reliably handling data succession, particularly when retiring systems, due to complexity and manual processes that can disrupt services and violate compliance obligations.

Innovation Solution

A declarative, policy-based approach for data succession is introduced, allowing for automated data evacuation plans that account for placement, transport, and transformation decisions, ensuring minimal disruption and compliance with specified requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual data succession processes are used when retiring systems, then flexibility in handling individual cases is maintained, but service disruptions increase and compliance obligations may be violated

Engineering Contradiction:
Improveservice continuityVSAvoiddata succession process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically identifies data requiring evacuation, selects destination systems, executes migration, and verifies completion without human intervention. The declarative policy framework enables the system to self-manage the entire data succession process, eliminating manual operations that cause service disruptions while maintaining compliance through automated policy enforcement.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Data evacuation is performed automatically before the source system is retired, ensuring data is migrated to destination systems and made accessible before the old system shuts down. This preliminary action prevents service disruptions by ensuring continuity of data access throughout the retirement process.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If automated data evacuation is implemented, then service disruptions are reduced and compliance is ensured, but the complexity of setting up the system increases

Engineering Contradiction:
Improvedata migration efficiencyVSAvoidautomation system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system uses declarative policies that define data characteristics (such as data type, compliance requirements, destination preferences) as parameters. By changing the approach from procedural automation to parameter-based declarative specification, the system reduces the complexity of setting up automation while maintaining high productivity. Users simply declare what they want achieved rather than programming complex automation logic.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If comprehensive data succession planning is performed, then compliance obligations are met, but the time required for system retirement increases

Engineering Contradiction:
Improvecompliance adherenceVSAvoidsystem retirement time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system continuously monitors data migration progress, verifies compliance requirements are met, and adjusts the evacuation process in real-time. This feedback mechanism ensures compliance obligations are satisfied while optimizing the migration timeline to minimize system retirement time. The automated verification provides immediate feedback on compliance status without requiring lengthy manual audits.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11816076B2Declarative data evacuation for distributed systems
Publication Date: 2023.11.14 SALESFORCE INC
  • US11816076B2 patent drawing
  • US11816076B2 patent drawing
  • US11816076B2 patent drawing

AI summary

A request may be received to evacuate data from a database system associated with a designated computing pod that provides on-demand computing services to a plurality of entities via the internet. The data may include portions that each correspond with a respective one or more of the on-demand computing services. Data succession policies associated with the data may be identified, where each data succession policy corresponds with one of the data portions and identifies one or more constraints associated with evacuating the data portion. The data portions may be transmitted to recipient computing pods in accordance with the data succession policies, and removed from the database system.