Master Data Replication in SaaS via Intermediary Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software-as-a-service (SAAS) systems face challenges in synchronizing and replicating master data from remote databases to local applications, particularly in scenarios where data needs to be shared across different entities and locations, while maintaining data security and integrity.
Innovation Solution
A method and apparatus for replicating, converting, and synchronizing master data between a remote master database and a SAAS application, using business objects (BOs) that include data conversion and synchronization mechanisms, such as export and import BO managers, to ensure data consistency and security across different systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If master data is replicated from a remote database to a SaaS application, then data accessibility and real-time updates are improved, but data security and control are worsened
Solution Approach 1:
The patent implements an intermediary synchronization mechanism that acts as a mediator between the remote master database and the local SaaS application. This intermediary layer enables data replication and real-time updates while maintaining security control, as it manages the data exchange process without requiring direct access to the sensitive master data, thus resolving the contradiction between accessibility and security.
Solution Approach 2:
The patent segments the data system into distinct components: a remote master database, a local SaaS application, and a synchronization mechanism. This segmentation allows the master data to remain secured in the remote database while replicated portions are used locally for operations, enabling both security maintenance and data accessibility improvement simultaneously.
2Speed
If direct access to remote master database is implemented, then data real-time synchronization is improved, but system complexity and security risks are worsened
Solution Approach 1:
The synchronization mechanism serves as an intermediary that simplifies the system architecture by providing a standardized interface between the remote database and local application. This intermediary handles the complexity of real-time synchronization internally, allowing fast data exchange without requiring the end system to manage the complexity of direct database access protocols and security mechanisms.
Data Source
AI summary
According to one general aspect, a method may include replicating, to a software-as-a-service application, a plurality of pieces of master data from a physically remote master database. The method may also include converting the plurality of pieces of master data into one or more pieces of local data of the software-as-a-service application. The method may include changing one or more of either the pieces of master data or the pieces of local data. The method may further include synchronizing the changed pieces of either master data or local data between the remote master database and the software-as-a-service application.