User-Extensible Common Schema in Shared Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database systems require separate databases for each customer, leading to inefficiencies when multiple companies need to share data, as they often rely on copying entire data sets, even when using third-party services, and current data marketplaces provide data independently for individual consumption.
Innovation Solution
Implementing a system that provides shared data sets for multiple users by using a common shared database, where changes are tracked in a delta table to allow individual users to modify data without affecting others, and enabling third-party management of overwrites while maintaining the original data set for all users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate databases are used for each customer, then data isolation and security are improved, but data sharing efficiency and system resource utilization deteriorate
Solution Approach 1:
The patent merges multiple customer databases into a single shared database system, allowing multiple tenants to access and share data through a common schema. This eliminates the need for separate database instances while maintaining data isolation through schema-level segmentation, thereby improving data sharing efficiency and resource utilization while preserving reliability.
Solution Approach 2:
The shared database system provides universal access to multiple customers through a common schema that can be extended by each tenant. This multi-functional approach allows different customers to use the same database infrastructure with customized schemas, improving both data sharing capability and system versatility.
2Ease of operation
If entire data sets are copied for sharing, then data accessibility is improved, but data redundancy and storage requirements worsen
Solution Approach 1:
The patent segments data access at the schema level rather than copying entire datasets. Each customer can access and modify only the portions of data relevant to them through schema extensions, eliminating unnecessary data redundancy while maintaining ease of access to shared data resources.
Solution Approach 2:
The common schema acts as an intermediary layer between the shared database and individual customers. This mediator allows customers to access and customize data without copying the entire dataset, reducing storage requirements while maintaining data accessibility through the schema interface.
3Productivity
If a common shared database is used, then system resource utilization and data sharing efficiency are improved, but data consistency and conflict management deteriorate
Solution Approach 1:
The patent implements dynamic schema extensions that allow customers to customize the common schema according to their needs. This dynamic approach maintains data consistency across the shared database while allowing individual customization, resolving the conflict between resource utilization efficiency and data consistency reliability.
Solution Approach 2:
The system changes the parameter of data organization from complete dataset copies to schema-level abstractions. This parameter change enables efficient resource utilization while maintaining data consistency through schema-based data definition and validation mechanisms that ensure consistent data structures across all customers.
4Ease of operation
If individual users can modify data directly, then operational flexibility is improved, but data integrity and version control worsen
Solution Approach 1:
The patent implements feedback mechanisms through schema validation that monitor and control data modifications. When users modify data, the system validates changes against the common schema definitions, providing feedback that ensures data integrity is maintained while allowing operational flexibility within defined parameters.
Solution Approach 2:
The common schema is established as a preliminary framework before data modification occurs. This preliminary structure defines the rules and constraints for data integrity, allowing users to perform flexible operations while the pre-established schema ensures data consistency and provides version control through schema evolution.
Data Source
AI summary
A user-extensible common schema is described in the context of a shared database. In one example, an apparatus includes a shared database organized around a common schema. First and second applications provides access to the shared database using the common schema, the first and second applications having first and second schema extensions having first and second sets of additional objects, defined by the first and second applications, respectively. The first and second applications present views of and operations on the shared database that are extended by the respective schema extension.