Persistent Library Bundle Data Persistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software applications require repeated invocation of functionalities provided by libraries at application restart, leading to time-consuming processes and reduced performance due to lack of data persistence.
Innovation Solution
The development and use of persistent library bundles (PLBs) that include pre-written source code and persistence descriptions, allowing automatic download and installation of libraries, enabling data persistence across application restarts through a cloud platform with a central registry and installation service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If functionalities provided by libraries are not persisted, then the application can be restarted cleanly, but the functionalities have to be repeatedly invoked at application restart which is time consuming and reduces application performance
Solution Approach 1:
The patent applies preliminary action by persisting library functionalities to storage memory devices before application restart. The persistence service pre-processes and stores library code in a persistent format, so that when the application restarts, the functionalities are already available in storage and can be quickly loaded without repeated invocation, thus resolving the time loss during restart while maintaining reliability
2Productivity
If library functionalities are repeatedly invoked at application restart, then data can be loaded into execution environment, but the process is time consuming and significantly reduces application performance
Solution Approach 1:
The persistence service performs preliminary actions by pre-compiling and persisting library functionalities to storage memory devices in an optimized format. This eliminates the need for repeated invocation at runtime, as the persisted code can be directly loaded into the execution environment, significantly improving application performance and reducing the time required for functionality loading
3Reliability
If applications store runtime data to storage memory devices, then data can be accessed after applications are closed, but the persistence mechanism adds complexity to the application structure
Solution Approach 1:
The patent introduces a persistence service as an intermediary between the application and storage memory devices. This mediator handles all persistence operations centrally, managing the complexity of data storage, retrieval, and library persistence. The application itself remains simple while the persistence service absorbs the structural complexity, thus maintaining reliability without significantly increasing application structure complexity
Data Source
AI summary
A persistent library bundle (PLB) is added as a library of an application. The PLB is automatically downloaded from a central registry and installed in an application directory. The PLB provides an out-of-the-box functionality to the application. The PLB includes a PLB persistence description. The PLB persistence description specifies how runtime data of the PLB has to be persisted. Upon installation of the PLB to the application, the PLB persistence description is copied to an application database directory. The application database directory stores application persistence description and the PLB persistence description. The application persistence description and the PLB persistence description are assigned to a certain database schema.