Secondary Database Delete Sync with Primary Record Inquiry

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The challenge in cloud computing environments is ensuring data reliability and availability while managing the overhead of maintaining synchronized backup copies of data, particularly in large databases, where delete operations often lead to state divergence between primary and secondary databases.

Innovation Solution

A mechanism is implemented to synchronize delete operations by proactively inquiring the primary database about which records in the secondary database are delete-able, sending a message to identify these records, receiving a response, and then deleting them from the secondary database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If backup copies are stored to ensure data reliability, then data reliability is improved, but system overhead increases

Engineering Contradiction:

Improvedata reliabilityVSAvoidsystem overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The secondary database autonomously manages its own synchronization by proactively inquiring the primary database about delete-able records. This self-service approach eliminates the need for the primary database to actively push delete notifications, reducing the primary database's workload and system overhead while maintaining data reliability through automated backup synchronization.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Instead of the conventional approach where the primary database pushes delete operations to the secondary database, this invention inverts the communication direction. The secondary database sends inquiry messages to the primary database to determine which records can be deleted, thereby reducing the primary database's processing burden while maintaining synchronization.

Inventive Principle:

Principle #13The other way round (Inversion)

2Reliability

If backup copies are kept synchronized with primary versions, then data reliability is improved, but processing overhead increases

Engineering Contradiction:

Improvedata reliabilityVSAvoidprocessing overhead

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The synchronization logic is extracted from the primary database and implemented independently in the secondary database. The secondary database takes out the burden of tracking and propagating delete operations by autonomously inquiring the primary database, thereby reducing the primary database's processing overhead while maintaining data reliability through independent backup management.

Inventive Principle:

Principle #2Taking out (Extraction)

3Stability of the object's composition

If delete operations are synchronized from primary to secondary database, then data consistency is improved, but primary database burden increases

Engineering Contradiction:

Improvedata consistencyVSAvoidprimary database burden

Core Design Contradiction:

Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The invention inverts the traditional synchronization direction by having the secondary database query the primary database for delete-able records rather than the primary database pushing delete operations. This inversion maintains data consistency between primary and secondary databases while significantly reducing the primary database's processing burden and operational complexity.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS12475082B2System and method for synchronizing delete operations between primary and secondary databases

Publication Date: 2025.11.18 SALESFORCE INC

AI summary

System and methods are described for synchronization of delete operations between primary a secondary databases. The method includes identifying a chunk of records in a secondary database. The method also includes sending a message to a primary database that identifies the chunk of records and asks whether any records of the chunk records are delete-able. The method also includes receiving a response to the message from the primary database. The response indicates which records of the chunk records are delete-able. The method also includes deleting each record of the chunk of records from the secondary database that the message indicated was delete-able.