Delta Replica Database Resource Reduction

Solution Overview

Problem

Current cloud-based database systems require significant computing resources to support multiple replicas for ensuring database availability, as each secondary replica consumes similar resources to the primary replica, despite most not being utilized.

Innovation Solution

Implementing delta replicas that maintain only transactional log files, reducing computing and storage requirements while maintaining quorum support for data integrity in case of primary replica failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple secondary replicas are deployed to ensure database availability, then reliability is improved, but computing and storage resources are significantly increased

Engineering Contradiction:

Improvedatabase availabilityVSAvoidcomputing resources

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent creates a lightweight copy of the transaction log (delta replica) rather than a full database replica. This delta replica contains only the transaction logs needed for recovery, significantly reducing storage and computing resources while maintaining the ability to restore the primary replica in case of failure.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent segments the replica into two types: full secondary replicas (for read operations and availability) and delta replicas (for recovery purposes). This segmentation allows the system to maintain reliability through multiple full replicas while using resource-efficient delta replicas for recovery, optimizing the balance between reliability and resource consumption.

Inventive Principle:

Principle #1Segmentation

2Reliability

If multiple full secondary replicas are maintained for quorum support, then data integrity is improved, but storage requirements are significantly increased

Engineering Contradiction:

Improvedata integrityVSAvoidstorage resources

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent creates a lightweight copy of the transaction log (delta replica) rather than a full database replica. This delta replica contains only the transaction logs needed for recovery, significantly reducing storage and computing resources while maintaining the ability to restore the primary replica in case of failure.

Inventive Principle:

Principle #26Copying

3Use of energy by moving object

If delta replicas are used instead of full secondary replicas, then computing and storage resources are reduced, but quorum support capability is compromised

Engineering Contradiction:

Improvecomputing resourcesVSAvoidquorum support

Core Design Contradiction:

Use of energy by moving objectVSReliability

Solution Approach 1:

The patent segments the replica into two types: full secondary replicas (for read operations and availability) and delta replicas (for recovery purposes). This segmentation allows the system to maintain reliability through multiple full replicas while using resource-efficient delta replicas for recovery, optimizing the balance between reliability and resource consumption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The delta replica serves multiple functions: it provides quorum support for write operations, enables recovery of the primary replica, and reduces resource consumption. By making the replica structure multi-functional, the system achieves both resource efficiency and maintained reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11846976B2Techniques for stateful persisted service resource reduction

Publication Date: 2023.12.19 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A data processing system implements techniques for provisioning and operating databases including receiving a request to provision a new database that includes multiple replicas. The data processing system provisions the new database including the plurality of replicas. The plurality of replicas includes a primary replica, one or more secondary replicas, and one or more delta replicas. The primary replica is configured to handle read and write operations. The one or more secondary replicas include a copy of data and transactional log information of the primary replica and are unable to handle write operations. The one or more delta replicas are a copy of the transactional log information of the primary replica and are unable to handle read operations or write operations.