Centralized Database Schema Linking for Distributed Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed database systems face issues with synchronization and replication errors, leading to instability and inconsistency between servers, which affect data reliability and require complex modifications for legacy applications.
Innovation Solution
Implementing a shared central database with central schema information that allows all machines to access data directly, eliminating the need for synchronization and enabling seamless integration of legacy applications without modification, using database linking technologies like synonyms and views.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored locally in each backend server database, then each server can independently manage its data, but synchronization and replication errors occur leading to data inconsistency between servers
Solution Approach 1:
The patent consolidates multiple distributed databases into a single centralized database, eliminating the need for synchronization between servers. All backend servers access the same central database instance, ensuring data consistency without replication complexity.
Solution Approach 2:
The centralized database acts as an intermediary between backend servers and frontend servers. All data access requests are routed through this single point, ensuring consistent data retrieval and eliminating synchronization issues that arise from direct server-to-server data sharing.
2Ease of operation
If schema information is maintained independently in each backend database, then each database can be managed separately, but replication and synchronization processes become error-prone and fragile
Solution Approach 1:
The patent merges schema information from multiple independent databases into a single centralized schema. This unified schema is maintained in the centralized database, eliminating replication errors while preserving the ability to manage different data types and structures through a single coherent framework.
Solution Approach 2:
The centralized database schema is designed to accommodate multiple data types and structures from different backend servers through a universal framework. This allows independent management of diverse data sources while ensuring consistent access and eliminating synchronization conflicts.
3Reliability
If a centralized database is implemented for all machines, then data consistency is improved and synchronization is eliminated, but legacy applications require modifications to access centralized data
Solution Approach 1:
The centralized database implements an intermediary layer with compatibility interfaces that allow legacy applications to access centralized data without modification. This mediator layer handles the translation between legacy access patterns and the new centralized architecture, preserving backward compatibility while enabling data consistency.
Solution Approach 2:
The system is segmented into distinct layers: the centralized database core and the compatibility interface layer. This segmentation allows the core to enforce data consistency while the interface layer handles legacy application requirements, enabling both goals to coexist without conflict.
4Productivity
If synchronization processes are implemented between backend servers, then data can be replicated across servers, but the processes are error-prone and fragile
Solution Approach 1:
The patent extracts the synchronization function entirely from the system by eliminating distributed data storage. Instead of replicating data across servers and synchronizing changes, all servers access the single centralized database instance directly, removing the synchronization component that causes errors and instability.
Data Source
AI summary
A method for converting a distributed system includes providing a central database in communication with a database, in which the central database includes central schema information for accessing data stored in the central database. The method further includes transferring content data and schema information from the database to the central database for storage. The method further includes connecting schema information stored in the database to the central schema information such that each database is configured to receive a request for information, redirect the request from the database to the central database based on the referenced schema information, and receive, from the central database, the requested information.