Segmented Application Architecture for Library Version Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application architectures that rely on third-party vendor frameworks face issues due to mismatches between library versions used by the vendor framework and custom applications, leading to inoperative functionality and potential violations of industry standards like PCI DSS.
Innovation Solution
Implementing a segmented application architecture that isolates applications from libraries by using separate program address spaces for vendor applications and custom components, allowing them to use distinct library versions through inter-process communication via Java Remote Method Invocation (RMI) interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a monolithic application architecture is used where vendor frameworks and custom applications share the same program address space, then ease of operation and simplicity of deployment are improved, but library version conflicts occur causing inoperative functionality and compliance violations
Solution Approach 1:
The patent divides the application architecture into separate program address spaces: one for vendor framework components and another for custom application components. Each address space loads and executes its own library versions independently, preventing version conflicts while maintaining operational reliability.
2Reliability
If separate program address spaces are used for vendor applications and custom components, then library version conflicts are prevented ensuring functional operability, but device complexity increases due to inter-process communication requirements
Solution Approach 1:
The patent introduces an application programming interface (API) as an intermediary layer between components in different program address spaces. This API enables standardized inter-process communication, allowing custom components to interact with vendor frameworks without direct memory access, thus managing complexity while maintaining isolation.
3Ease of manufacture
If custom applications share the same library versions as vendor frameworks, then ease of manufacture and simplicity of maintenance are improved, but adaptability to different library versions is lost causing compliance violations
Solution Approach 1:
The patent segments the library loading process so that custom application components load their own required library versions in their dedicated program address space, independent of the vendor framework's library versions. This allows custom components to adapt to different library versions as needed while vendor frameworks maintain their own versioning.
Data Source
AI summary
An operationally monolithic application is provided, where the application resides in a first program address space of an application server. The application calls to an application component residing in a second program address space of the application server, the application component being built upon a framework of the operationally monolithic application. The operationally monolithic application loads at least a first library upon which it depends to invoke a first method, and the application component loads at least a second library upon which it depends to invoke a second method. The first and second libraries can co-exist on the application server despite being different versions of the same libraries.