Deployment Plugin Architecture for Database Object Version Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The deployment of business process objects in database systems is complex and inefficient due to the need for version control, lifecycle management, and dependency management, hindering the implementation of database systems.
Innovation Solution
A computer-implemented method using a build plugin component to define, determine dependencies, create, and deploy database objects during runtime, with a transactional all-or-nothing deployment model, and the use of containers for isolation and incremental deployment scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional deployment processes are used for database objects, then version control and lifecycle management can be achieved, but deployment complexity significantly increases
Solution Approach 1:
The patent introduces a deployment plugin as an intermediary component that mediates between the development environment and the database system. This plugin handles version control, dependency management, and deployment operations, thereby achieving reliable version control while shielding users from deployment complexity. The plugin acts as a specialized tool that automates complex deployment tasks.
Solution Approach 2:
The deployment process is designed to be self-service through automated dependency resolution and incremental deployment capabilities. The system automatically determines dependencies between database objects and executes deployments in the correct sequence without requiring manual intervention. This self-service mechanism maintains version control reliability while reducing deployment complexity.
2Reliability
If comprehensive dependency management is implemented for database objects, then deployment consistency is improved, but processing time increases
Solution Approach 1:
The patent implements preliminary action by pre-determining and caching dependency relationships between database objects during development. The deployment plugin analyzes and stores the dependency graph in advance, so that during actual deployment, the system can quickly retrieve pre-computed deployment sequences without performing complex real-time analysis. This ensures deployment consistency while minimizing processing time.
Solution Approach 2:
The deployment process is segmented into independent, manageable units based on dependency relationships. Instead of deploying all database objects simultaneously, the system divides them into deployment batches according to their dependencies, allowing parallel processing of independent segments. This segmentation maintains deployment consistency through proper sequencing while reducing overall processing time through parallel execution.
3Reliability
If all database objects are deployed in a single transaction, then transactional integrity is ensured, but deployment flexibility is reduced
Solution Approach 1:
The patent segments the deployment transaction into multiple atomic units based on dependency groups. Each segment represents a set of database objects that can be deployed together in a single transaction. The deployment plugin manages these segments sequentially, ensuring that each segment maintains transactional integrity while the overall deployment process remains flexible and can be paused, rolled back, or continued based on success or failure of individual segments.
Solution Approach 2:
The deployment transaction structure is made dynamic rather than static. The system can adaptively adjust the transaction scope based on dependency analysis and deployment context. If a deployment fails, the system can dynamically rollback only the affected segments rather than the entire deployment, providing flexibility while maintaining transactional integrity for each atomic unit.
Data Source
AI summary
A system, a method, and a computer program product for deploying objects are disclosed. A file containing a plurality of artifacts for deploying during runtime of an application is defined. At least one dependency for at least one artifact in the plurality of artifacts is determined based on the defined file. A database object for implementation during runtime of the application is created based on the determined dependency. At least one change to the database object during runtime of the application is implemented. The artifact is deployed during runtime of the application based on the implemented change to the database object.