Consumer-to-Producer Database Writes with Metadata and Topology Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database migration techniques do not allow producers to maintain control over database data management, leading to inconsistencies and geographical access challenges, and lack flexibility in handling different database topologies and user permissions.
Innovation Solution
Implementing a system that enables writes from a consumer database to a producer database while maintaining control over metadata and transaction context, allowing access based on local user ID mappings, and supporting different database topologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If database migration techniques are used to allow consumer databases to access producer databases, then data accessibility is improved, but producer control over data management is lost leading to inconsistencies
Solution Approach 1:
The patent introduces a metadata service as an intermediary between consumer databases and producer databases. This service manages the metadata that defines database structure, constraints, and access rules, allowing consumer databases to access producer data while the metadata service maintains producer control and ensures data consistency through centralized metadata management.
2Quantity of substance
If database systems are scaled to handle increasing data amounts, then data storage capacity is improved, but system complexity and maintenance cost increase
Solution Approach 1:
The patent segments the database system into distinct components: producer databases that own and manage data, consumer databases that access data, and a metadata service that manages coordination. This segmentation allows the system to scale storage capacity by adding more producer or consumer databases without proportionally increasing overall system complexity, as each component has a defined role and responsibility.
Solution Approach 2:
The metadata service provides universal functionality that serves multiple purposes: it manages database schemas, controls access permissions, validates data operations, and coordinates transactions across multiple databases. This multi-functionality reduces the need for separate management systems for each database, thereby reducing overall system complexity while enabling scalable data storage.
3Adaptability or versatility
If different database topologies are supported to increase flexibility, then adaptability is improved, but handling complexity across topologies increases
Solution Approach 1:
The patent uses metadata as a parameter-based configuration system that describes database topologies, relationships, and access patterns. By representing different database topologies as configurable metadata parameters rather than hard-coded structural requirements, the system can support multiple topologies (star, mesh, hierarchical) without increasing management complexity. The metadata service processes these parameters uniformly regardless of the specific topology being configured.
Data Source
AI summary
A consumer database of a service provider network may perform writes to a producer database. To do so, the consumer database obtains metadata and a transaction context from the producer database and uses that information to perform a write from the consumer database to the producer database. A consumer database may access (read and/or write) a producer database that uses a different topology to manage data. To do so, the consumer database obtains topology metadata from the producer database and uses the topology metadata to perform a query (read or write) from the consumer database to the producer database. A consumer database may access a producer database based on a mapping of local user IDs to consumer databases at the producer database. The access may be granted to the consumer database based on permissions assigned to the local user IDs.