Containerized Processing Framework for In-System Programming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of managing software development lifecycles, particularly in migrating software applications from one environment to another, often requires significant manual adjustments and re-development, leading to increased resources and downtime, as existing systems lack efficient tools for synchronizing design time and runtime artifacts in containerized environments.
Innovation Solution
A processing framework is implemented within a containerized environment that uses declarative artifacts to define target states for runtime artifacts, allowing for in-system programming to update running applications without re-deployment, by creating model definition objects and scanning for necessary operations to align with target states defined in declarative artifacts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual adjustments and re-development are performed to migrate software applications between environments, then the software can be updated to new versions, but resource consumption and downtime increase significantly
Solution Approach 1:
The patent creates model definition objects that serve as templates or copies of the desired target state from declarative artifacts. These model objects are then scanned and compared against runtime artifacts to identify discrepancies, allowing the system to generate synchronization operations without manual re-development. This copying approach eliminates the need for resource-intensive manual adjustments while maintaining software update capability.
2Adaptability or versatility
If manual adjustments and re-development are performed to migrate software applications between environments, then the software can be updated to new versions, but the time required for migration increases
Solution Approach 1:
The patent performs preliminary actions by creating model definition objects from declarative artifacts before the actual migration or update process. The system scans and compares these model objects with runtime artifacts in advance, identifying all necessary synchronization operations beforehand. This preliminary preparation eliminates the need for time-consuming manual adjustments during migration, significantly reducing migration time while maintaining software update capability.
3Device complexity
If existing systems are used without synchronization tools, then system simplicity is maintained, but the complexity of managing software development lifecycles increases
Solution Approach 1:
The patent introduces an intermediary processing framework that acts as a mediator between declarative artifacts and runtime artifacts. This framework automatically scans, compares, and generates synchronization operations to align runtime artifacts with the target state defined in declarative artifacts. The intermediary handles the complexity of lifecycle management internally, maintaining simple system structure while dramatically improving ease of operation for software updates and migrations.
4Manufacturing precision
If re-deployment is performed to update software applications, then the target state can be achieved, but downtime and unavailability increase
Solution Approach 1:
The patent enables dynamic updates by allowing synchronization operations to be executed on running systems without requiring re-deployment. The processing framework generates and applies operations that modify runtime artifacts in-place while the system remains operational. This dynamic approach maintains precise target state accuracy while preserving system availability, eliminating the downtime associated with traditional re-deployment methods.
Data Source
AI summary
The present disclosure relates to computer-implemented methods, software, and systems for lifecycle processing of declarative artifacts. Declarative artifacts defining a target state for application content related to a software application are read. When running, the software application includes runtime artifacts executing in a containerized environment. Model definition objects for processing during runtime of the software application based on the declarative artifacts are created and stored in a model repository at a container associated with the software application. The model repository is scanned as well as the runtime artifacts executing as part of the software application in the containerized runtime environment to identify a model definition object from the model repository for processing at runtime of the software application. An operation related to a runtime artifact to run as part of the running software application at the containerized runtime environment is executed based on input from the identified model definition object.