Database Transaction Log Service Consolidation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database systems face challenges in scaling to handle increasing numbers of clients, read and write queries, data volume, and storage devices, leading to resource exhaustion and performance degradation due to high memory and I/O demands.

Innovation Solution

A scalable database transaction log service is implemented, enabling asynchronous processing of log requests, consolidating transaction log requests and logs, and performing egress validation to reduce resource consumption and ensure data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If database systems scale to handle increasing numbers of clients, queries, and data volume, then the system capacity and throughput are improved, but memory and I/O resources are exhausted leading to performance degradation

Engineering Contradiction:
Improvesystem capacityVSAvoidmemory and I/O resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

Multiple transaction log requests are merged into a single consolidated read request. The log service receives multiple individual log requests from different clients, consolidates them into one aggregated request, and retrieves all required transaction logs in a single I/O operation from storage, thereby reducing the total number of I/O operations and memory allocations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The log service acts as a universal intermediary that handles multiple client requests through a single consolidated operation. This multi-functional approach allows the system to serve multiple clients simultaneously through one I/O operation, improving resource utilization and reducing the overall burden on storage and memory resources.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of operation

If individual transaction log requests are processed separately for each client, then request handling simplicity is maintained, but I/O operations and memory consumption increase

Engineering Contradiction:
Improverequest handlingVSAvoidI/O operations
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

Individual log requests from multiple clients are merged into a single consolidated request. The log service maintains simplicity by providing a uniform interface for receiving requests while internally consolidating them into one I/O operation, thus reducing I/O overhead without significantly complicating the request handling process.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If transaction logs are stored on multiple storage devices, then data distribution and scalability are improved, but the number of I/O operations and system complexity increase

Engineering Contradiction:
Improvedata distributionVSAvoidstorage system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The log service acts as an intermediary between clients and the distributed storage system. It receives consolidated log requests, determines which storage devices contain the required transaction logs, and coordinates the retrieval process. This intermediary approach simplifies the complexity of accessing distributed storage by providing a unified access point while maintaining the benefits of data distribution across multiple devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11709824B2Consolidating transaction log requests and transaction logs in a database transaction log service
Publication Date: 2023.07.25 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11709824B2 patent drawing
  • US11709824B2 patent drawing
  • US11709824B2 patent drawing

AI summary

Methods, systems, and computer program products are provided for consolidating transaction log requests and transaction logs in a database transaction log service. A scalable log service may manage log requests and logs to reduce resource consumption, such as memory and I/O. Log requests may be managed by consolidating (e.g., organizing, merging and/or de-duplicating) the log requests. Transaction log requests may be mapped to read requests for transaction log storage devices in less than a one-to-one ratio. Transaction logs may be managed by using the consolidated log requests to consolidate (e.g., and prefetch) transaction logs from multiple cache and/or storage tiers to a log pool cache. Log requests may be served from the log pool cache.