Connection Multiplexing for Parallel Database Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The manual deployment of hundreds or thousands of database artifacts in complex database systems is time-consuming and difficult due to the complexity of relationships between development artifacts and run-time database objects, requiring a more efficient and automated approach for deployment.
Innovation Solution
A deployment infrastructure system that uses a declarative approach and parallel processing to deploy database artifacts in a self-organizing manner, providing a transactional all-or-nothing deployment model with implicit dependency management, and employing connection multiplexing to optimize database interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual deployment of database artifacts is performed, then deployment accuracy and dependency management are maintained, but deployment time and productivity are significantly reduced
Solution Approach 1:
The system automatically determines deployment order by analyzing dependencies between artifacts, and autonomously manages the deployment process without manual intervention. The deployment infrastructure service layer self-organizes the deployment of hundreds or thousands of artifacts by identifying relationships and executing in the correct sequence, eliminating the need for manual planning and coordination.
Solution Approach 2:
The patent replaces manual mechanical deployment processes with an automated software-based deployment infrastructure. The service layer uses algorithms to analyze dependency graphs and automatically sequences deployment operations, substituting human operators with an intelligent system that can process thousands of artifacts efficiently and accurately.
2Loss of time
If parallel processing is used to deploy database artifacts, then deployment time is reduced, but database connection management complexity increases
Solution Approach 1:
The patent merges multiple database connections into a single shared connection that is reused across parallel worker threads. Instead of each worker maintaining its own connection, the system consolidates connection management at the service layer, allowing multiple workers to share the same database connection safely through coordinated access and transaction management.
Solution Approach 2:
The single database connection is designed to serve multiple functions and multiple worker threads simultaneously. The connection becomes a universal resource that can handle deployment operations for different artifacts in parallel, with the service layer coordinating access to ensure data consistency and proper transaction boundaries.
Data Source
AI summary
Systems and methods are disclosed for connection multiplexing in a parallel processing environment. An example method includes requesting, responsive to a request to perform multiple database operations in a single transaction, a connection identifier for a physical connection to the database, providing the connection identifier to each of a plurality of workers, and performing the multiple database operations using the plurality of workers. Each worker may obtain a work item from a work queue, initiate a database request for the work item, and provide the database request to a database server. The database request represents one of the multiple database operations and includes the connection identifier. The database server may determine that the connection identifier corresponds to the physical connection, add the request to a connection queue associated with the physical connection, and execute requests from the connection queue against the database via the physical connection.