Runtime Data Corruption Detection in Multitenant Platforms

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In large-scale cloud-based systems, manual detection of data corruptions in custom indexes and skinny tables is inefficient, leading to resource wastage, prolonged downtimes, and trust issues due to the inability to accurately identify and correct corruptions in real-time.

Innovation Solution

A runtime corruption detection platform that uses callback hooks and context examination to identify and log data corruptions in custom indexes and skinny tables, allowing for automatic or manual correction and minimizing disruption by flagging or failing transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual detection methods are used to identify data corruptions, then detection accuracy can be maintained through expert supervision, but resource efficiency deteriorates due to prolonged downtimes and inefficient use of resources

Engineering Contradiction:

Improvedetection accuracyVSAvoidresource efficiency

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The system enables self-service through automated corruption detection mechanisms that operate without continuous manual intervention. Corruption detection code is automatically injected into database operations, and the system self-monitors for corruptions in real-time, eliminating the need for constant expert supervision while maintaining high detection accuracy

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Manual detection mechanisms are replaced with automated computational systems. The patent substitutes human expert supervision with algorithm-based corruption detection that continuously monitors database operations, replacing the mechanical process of manual checking with an automated electronic detection system

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If intensive manual supervision is implemented to identify corruptions, then detection thoroughness is improved, but time consumption increases leading to prolonged downtimes

Engineering Contradiction:

Improvedetection thoroughnessVSAvoiddowntime

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary corruption detection by injecting detection code into database transactions before they complete. Corruptions are identified during the transaction execution itself rather than after completion, allowing for immediate detection and rollback without prolonged downtimes

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The corruption detection operates continuously throughout database operations rather than in periodic manual checks. The detection mechanism runs concurrently with normal database transactions, providing continuous monitoring without interrupting the flow of useful work, thereby reducing overall downtime

Inventive Principle:

Principle #20Continuity of useful action

3Reliability

If maintenance code is generated to reduce corruptions, then prevention capability is improved, but detection completeness deteriorates as corruptions outside maintenance code remain undetected

Engineering Contradiction:

Improveprevention capabilityVSAvoiddetection completeness

Core Design Contradiction:

ReliabilityVSMeasurement precision

Solution Approach 1:

The corruption detection mechanism is designed to be universal, monitoring all database operations regardless of which specific maintenance code generated them. The detection system applies uniformly across all custom indexes and skinny tables, providing comprehensive coverage that transcends individual maintenance code boundaries

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The detection system is segmented and injected into individual transaction contexts rather than relying on monolithic maintenance code. By dividing the detection capability into discrete, injectable segments that operate at the transaction level, the system achieves complete coverage across all database operations without gaps

Inventive Principle:

Principle #1Segmentation

4Reliability

If continuous corruption monitoring is implemented, then data reliability is improved, but system complexity increases due to additional detection mechanisms

Engineering Contradiction:

Improvedata reliabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The corruption detection code is nested within existing database transaction structures rather than operating as a separate external system. Detection logic is embedded inside transaction contexts, allowing the monitoring function to be contained within the existing system architecture without adding significant external complexity

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentUS11238017B2Runtime detector for data corruptions

Publication Date: 2022.02.01 SALESFORCE INC

AI summary

In a multitenant data platform architecture, one or more supporting data tables are used to efficiently retrieve data responsive to data retrieval requests. Programmatic code markers associated with contextual data about a data transaction thread are identified. The contextual data is examined using the one or more programmatic code markers invoked by the database in the data transaction thread at runtime. Based on the contextual data returning an indication of a data corruption in one or more supporting data structures, an action associated with the data transaction thread is performed. A log of data corruptions and corresponding call stack trace data may be generated. The data transaction thread may be allowed to continue to execute statements that modify data tables, or the data transaction thread may be terminated.