Datacenter Data Placement Using Access-Pattern Latency Minimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication methods in distributed databases result in high latency and significant costs due to redundant storage and network traffic, while caching data locally leads to staleness and inefficient update operations.

Innovation Solution

Implementing a latency minimization layer (LML) that dynamically moves data between datacenters based on access patterns, using a plug-in to monitor and calculate metrics for data records, and selectively transferring them to optimize storage locations for reduced latency and network costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If data is distributed to multiple datacenters using distributed databases, then access latency is reduced, but storage costs and network traffic increase significantly

Engineering Contradiction:
Improveaccess latencyVSAvoidredundant storage and network traffic
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The patent applies local quality by making data placement dynamic and location-specific based on access patterns. Instead of uniformly distributing all data to all datacenters, the system monitors access patterns and selectively replicates data to specific datacenters where it is frequently accessed, thereby reducing redundant storage while maintaining low latency for hot data

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically adjusts data replication based on changing access patterns. The data placement is not static but adapts over time as access patterns evolve, allowing the system to optimize the balance between latency and redundancy dynamically rather than using a fixed distribution strategy

Inventive Principle:
Principle #15Dynamics

2Speed

If data is cached locally, then access speed is improved, but data staleness and update inefficiency occur

Engineering Contradiction:
Improveaccess speedVSAvoiddata freshness
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system implements feedback mechanisms by monitoring access patterns and using this information to make intelligent decisions about data placement. The feedback loop allows the system to distinguish between read-heavy and write-heavy data, placing read-heavy data closer to users for fast access while keeping write-heavy data centralized for freshness, thus resolving the staleness problem

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent changes the parameter of data placement from static to dynamic based on access pattern analysis. By adjusting placement decisions based on monitored parameters like read/write ratios and access frequency, the system can optimize both access speed and data freshness without the pitfalls of simple caching

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If remote data access is used across geographically disparate datacenters, then global data availability is achieved, but latency increases and impacts usability

Engineering Contradiction:
Improveglobal data availabilityVSAvoidaccess latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by proactively replicating data to datacenters where it is likely to be accessed based on historical access patterns. Instead of waiting for remote access requests to occur and then experiencing latency, the data is pre-positioned in appropriate locations, eliminating the latency penalty while maintaining global availability

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3971730B1Latency minimization in datacenters
Publication Date: 2026.02.04 SAP SE
  • EP3971730B1 patent drawingFigure 1
  • EP3971730B1 patent drawingFigure 2A
  • EP3971730B1 patent drawingFigure 2B

AI summary

Methods, systems, and computer-readable storage media for monitoring, by a LML plug-in to a first service executed within a first datacenter, accesses to provide access data representative of the accesses to a data record stored in the first datacenter, the accesses including local accesses executed by the first service and remote accesses executed by a second service executed within a second datacenter, receiving, by a LML instance executed within the first datacenter, the access data from the LML plug-in to the first service, determining, by the LML instance, a set of metrics for the data record based on the local accesses and the remote accesses in a first time period, and selectively executing a transfer process based on the set of metrics to copy the data record to the second datacenter.