Modular Application Resource Sharing via Cache and Database Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In modular applications, resources are often not shared among modules due to development differences and communication challenges, leading to redundant requests and storage overhead.
Innovation Solution
A system and method for sharing resources among modules by establishing a cache that stores resource identifiers and links them to a database storage position, allowing multiple modules to access shared resources efficiently without direct communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If resources are not shared among modules, then module independence and data security are maintained, but redundant resource requests and storage overhead increase
Solution Approach 1:
The system segments resource management into two distinct layers: a private cache layer for each module that maintains data isolation and independence, and a shared database layer that enables resource sharing. The private cache stores resource identifiers and links to the shared database, allowing modules to access shared resources without direct communication while maintaining their independence.
Solution Approach 2:
A shared database acts as an intermediary between multiple independent modules. Instead of modules directly communicating or sharing resources with each other, they all interact with the shared database through their private caches. This intermediary enables resource sharing while preserving module independence and data security.
2Reliability
If each module connects to its own server, then resource exclusivity is ensured, but communication complexity and time consumption increase
Solution Approach 1:
Multiple private caches from different modules are merged into a unified shared database structure. Instead of maintaining separate server connections for each module, the system combines resource storage into a single shared database that all modules can access through their respective cache layers, reducing communication complexity while maintaining resource exclusivity through the cache intermediary.
Solution Approach 2:
The private cache serves as an intermediary layer between the module and the shared database, abstracting away the complexity of direct module-to-module communication. Modules interact only with their private cache, which handles the complexity of accessing the shared database, thereby reducing communication complexity while ensuring resource exclusivity.
3Loss of substance
If resources are stored in a shared location, then storage efficiency is improved, but access control and data security become more difficult
Solution Approach 1:
The storage system is segmented into private cache segments for each module and a shared database segment. Each module's private cache maintains control over its own data access patterns and stores resource identifiers that link to the shared database. This segmentation enables storage efficiency through sharing while maintaining data security through modular access control points.
Data Source
AI summary
A system and method for sharing resources among application modules includes receiving, on an application including a plurality of modules, a resource from a server; determining a storage position identifier corresponding to an identifier of the resource and indicative of a storage position in a database for storing resources dedicated for the application; and storing the resource in the database based on the determined identifier for sharing among the plurality of modules.