Application Stack Read-Only Replica with Local Write Buffer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face inefficiencies and high costs in managing data replication within software application stacks due to the need for local changes to be synchronized with remote data, leading to inconsistencies and redundancy, especially in complex business processes.

Innovation Solution

Implementing a write-enabled buffer alongside a read-only replica in the application stack, where local updates are made in the buffer rather than the replica, with customizable prioritization rules to manage data access and synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a read-only replica is used to store copied data, then data consistency with the source system is maintained, but local updates and adjustments required by complex business processes are blocked

Engineering Contradiction:

Improvedata consistencyVSAvoidlocal update capability

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system segments the data storage into three distinct components: the source system, the read-only replica, and the write buffer. This segmentation allows each component to serve a specific function - the replica maintains consistency while the write buffer handles local updates, resolving the contradiction between data consistency and local update capability

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The write buffer acts as an intermediary between the read-only replica and the source system. It allows local updates to be performed without directly modifying the replica, thereby maintaining data consistency while enabling local changes through this intermediate layer

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If application-specific local replicas are created to enable local updates, then local modification capability is improved, but system complexity and synchronization effort increase

Engineering Contradiction:

Improvelocal modification capabilityVSAvoidsynchronization mechanism

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The write buffer extracts the update management function from the replica itself. By separating the update capability from the data storage, the system enables local modifications without requiring complex synchronization mechanisms, as updates are contained in the buffer until ready for controlled propagation

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Updates are performed preliminarily in the write buffer before being applied to the source system. This preliminary action allows local modifications to be prepared and validated without immediately affecting the source system, reducing synchronization complexity through staged updates

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If multiple developers work individually on separate local replicas, then application-specific customization is enabled, but redundancy and cost increase

Engineering Contradiction:

Improveapplication customizationVSAvoiddata redundancy

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The write buffer provides a universal mechanism that serves all applications requiring local updates. Instead of each application maintaining its own separate replica, the single write buffer serves multiple applications, reducing data redundancy while maintaining customization capabilities through the prioritization logic

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If frequent data lookups are performed remotely, then data integration is achieved, but access performance deteriorates due to physical distance and data volume

Engineering Contradiction:

Improvedata integrationVSAvoiddata access speed

Core Design Contradiction:

Adaptability or versatilityVSSpeed

Solution Approach 1:

Data is preliminarily copied to the read-only replica before access is needed. This preliminary action of replication allows subsequent lookups to be performed locally on the replica rather than remotely on the source system, significantly improving access speed while maintaining data integration

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12499053B2Application stack read-only replica with application specific write buffer

Publication Date: 2025.12.16 SAP SE

AI summary

According to some embodiments, a replication tool may arrange for a copy of original records from a data source to be written into a read-only replica in an application stack. Write buffer logic in the application stack may determine that information in an original record of the read-only replica has been locally updated at the application stack by application logic. The write buffer logic may then automatically create an updated version of the original record in a write buffer of the application stack based on the local update by the application logic. Moreover, prioritization logic may automatically determine whether information in the original record or the updated record will be accessed.