Master-Slave Data Sharing Across Networked Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current networked applications require data replication and duplication for sharing business data across different systems, leading to increased integration costs and efforts, as well as replication latency in reporting and analytics scenarios.

Innovation Solution

A method and system for sharing business data across networked applications based on a common platform, where a master application is designated to store data, allowing other applications to access and interact with it without replication, using a locking mechanism to ensure data integrity and consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data replication is used to share business data across networked applications, then data accessibility is improved, but integration costs and efforts increase

Engineering Contradiction:
Improvedata accessibilityVSAvoidintegration costs and efforts
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges data storage and data access functions into a unified architecture where a master application stores data and multiple slave applications access it through a common platform. This eliminates the need for separate data replication mechanisms in each application, reducing integration complexity while maintaining accessibility.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The common platform provides universal data access capabilities that work across multiple applications. Instead of requiring application-specific replication logic, the platform offers standardized interfaces and protocols that enable any application to access master data without complex integration efforts.

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

2Ease of operation

If data replication is used to share business data across networked applications, then data accessibility is improved, but replication latency increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidreplication latency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent extracts the data storage function from individual applications and consolidates it in a master application. By removing replication logic from the data access path and using direct access to the master copy through the common platform, the system eliminates replication latency entirely while maintaining data accessibility.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If data replication is used to share business data, then data sharing capability is improved, but data consistency and integrity deteriorate

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiddata consistency and integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the data access architecture into a clear master-slave model where the master application is the single source of truth for data consistency. The common platform handles access control and data retrieval, separating concerns to maintain integrity while enabling versatile sharing across applications.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8612406B1Sharing business data across networked applications
Publication Date: 2013.12.17 SAP SE
  • US8612406B1 patent drawing
  • US8612406B1 patent drawing
  • US8612406B1 patent drawing

AI summary

The present disclosure describes methods, systems, and computer program products for sharing business data across networked applications. The method for sharing business data across networked applications can include receiving a request associated with data object instance via a first business application. The data object instance is of a specific data object type. A second business application is identified as an assigned master business application associated with the requested data object instance. The first business application and the second business application are based on a common application platform. Data associated with the requested data object instance is accessed at the second business application.