Dynamic Configuration Directory for Multi-Tenant Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional multi-tenancy systems face scalability issues and inefficiencies due to hard-coded data storage locations, limiting data access across multiple sources and requiring costly server upgrades and re-coding for data relocation.
Innovation Solution
A dynamic configuration directory using connection strings and data adapters allows for seamless data access and storage based on business logic, enabling data relocation without re-coding, by utilizing a routing identifier and business entity identifier to determine the appropriate data storage location and type.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data storage locations are hard-coded into application configuration files or program code, then data access is simple and direct, but data relocation requires re-coding and the system lacks flexibility
Solution Approach 1:
The patent introduces a dynamic configuration directory as an intermediary layer between the application and data stores. This directory contains connection strings and data adapters that map logical data requests to physical storage locations. When data needs to be relocated, only the dynamic configuration directory needs to be updated, not the application code itself. The connection strings store location information and the data adapters handle data type information, allowing flexible data relocation without re-coding.
Solution Approach 2:
The patent implements dynamic configuration directories that can be updated at runtime without requiring system re-coding. The connection strings and data adapters are stored in a configurable format that allows administrators to modify data storage locations and access parameters dynamically. This transforms the static, hard-coded data access model into a dynamic one where data locations can change without affecting the application code.
2Productivity
If a single instance of data is used in multi-tenant applications, then server resource utilization is optimized, but scalability is limited and requires larger servers
Solution Approach 1:
The patent creates a universal data access architecture where a single application instance can access multiple data stores through the dynamic configuration directory. The connection strings and data adapters provide a unified interface that allows the same application to work with different data locations and types. This enables multi-tenant applications to scale across multiple servers and data stores without requiring separate application instances, thereby improving both resource utilization and scalability.
Solution Approach 2:
The patent segments the data storage architecture by allowing data to be distributed across multiple data stores while maintaining a unified access interface through the dynamic configuration directory. Each data store can be independently managed and scaled, and the connection strings enable the application to access segmented data across different locations. This segmentation allows the system to scale horizontally by adding more data stores without increasing application complexity.
3Ease of operation
If data for a particular client is stored on the same server, then data access is simplified, but the client cannot access data from multiple sources and the system lacks flexibility
Solution Approach 1:
The patent implements a configuration where the dynamic configuration directory can contain multiple connection strings and data adapters for the same client, allowing partial data access from multiple sources. The system can selectively use different data stores based on the specific data request, maintaining simplicity for common access patterns while enabling multi-source access when needed. This partial approach allows clients to access data from multiple sources without complicating the basic data access model.
Data Source
AI summary
A master dynamic configuration directory can store connection strings and data adapters for data entities based on a routing identifier and a business entity identifier. The information can be stored in multiple data stores, each of which can have a different data type. A data request from a requesting entity comprises a routing identifier and a business entity identifier. A system application can receive a data request and can access the local instance of the dynamic configuration directory to determine the corresponding connection string and data adapter based on the routing identifier and business entity identifier in the data request. The system sub-application creates a data access instance based on the connection string and data adapter. The system application loads the data access instance to access the data entity at the appropriate location and to perform a data function according to the data request.