Proxy Pluggable Database for Location Transparency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database management systems face challenges in maintaining locational transparency and efficient management of pluggable databases (PDBs) within container databases, leading to the need for constant application code rewriting and limitations in scaling due to hardware constraints.
Innovation Solution
The implementation of proxy pluggable databases and application root replicas, which allow for transparent location management of PDBs and enable efficient query optimization by forwarding commands and data across multiple container databases, using container maps for logical partitioning and query optimization techniques.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If pluggable databases are moved between container databases for load balancing or scaling, then system flexibility and scalability improve, but application code must be constantly rewritten to reflect new locations
Solution Approach 1:
The patent introduces a proxy pluggable database as an intermediary component that remains at a fixed location and forwards queries to the actual data-bearing PDB wherever it is located. This mediator absorbs the complexity of location tracking, allowing applications to interact with a stable proxy interface while the real PDB moves between container databases for load balancing or scaling purposes.
Solution Approach 2:
The proxy PDB creates a copy or representation of the actual PDB's interface and metadata at a fixed location. This copy contains the necessary information to locate and communicate with the real PDB, whether it resides in the local CDB or a remote one. The copy remains stationary while the original can move freely, solving the location transparency problem.
2Adaptability or versatility
If data is partitioned across multiple container databases to overcome hardware constraints, then system scalability improves, but data transfer overhead between databases increases
Solution Approach 1:
The patent segments the database system into multiple container databases, each hosting portions of the partitioned data. This segmentation allows the system to distribute data across multiple physical systems to overcome individual hardware constraints, achieving horizontal scalability while maintaining logical database integrity through the proxy mechanism.
Solution Approach 2:
The system performs preliminary actions by establishing proxy PDBs and container maps in advance, which pre-configured routing information and location metadata. This preliminary setup enables efficient query routing without requiring real-time location lookups, reducing data transfer overhead when accessing partitioned data across multiple CDBs.
3Ease of operation
If proxy pluggable databases are implemented to maintain location transparency, then application code stability improves, but system complexity increases
Solution Approach 1:
The proxy PDB serves as an intermediary layer that encapsulates the complexity of location management, container maps, and cross-CDB communication. Applications interact only with the simple, stable proxy interface, while the mediator handles the complex tasks of locating the real PDB, establishing connections, and transferring data, thereby isolating complexity from the application layer.
Solution Approach 2:
The proxy PDB and container map system operates autonomously to maintain location transparency. The proxy automatically tracks and updates the location of data-bearing PDBs, manages container map entries, and handles query routing without requiring application code changes. This self-service capability maintains code stability while managing the underlying complexity automatically.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In an approach, when a pluggable database within a container database is transported to a new container database, the pluggable database is replaced with a proxy pluggable database storing forwarding information for the pluggable database. When a command is received that is to be executed on the proxy pluggable database, the database server handling the command uses the forwarding information stored within the proxy pluggable database to forward the command to a second database receiver responsible for the new container database for execution on the pluggable database. The result of executing the command is then returned to the first database server. Thus, application code which references the pluggable database within the original container database does not have to be rewritten to reference the new location and can remain agnostic as to the actual location of the pluggable database.