Multi-Tenant Request Handling via Identifier Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems struggle to efficiently and accurately share applications among multiple tenants, as exclusive applications cannot meet increasing resource utilization demands.
Innovation Solution
A method and device that receive a user request, determine tenant information, modify application identifiers based on this information, and send a new request to enable quick and accurate sharing of applications among multiple tenants, utilizing a gateway to manage the mapping and modification of identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If exclusive applications are used to ensure application functionality and reliability, then application reliability is improved, but system resource utilization deteriorates
Solution Approach 1:
Multiple exclusive applications are merged into a single shared application instance that serves multiple tenants. The system combines resource isolation mechanisms with shared infrastructure, allowing different tenants to access the same application through modified identifiers while maintaining functional independence and reliability for each tenant.
Solution Approach 2:
A single application instance is designed to serve multiple tenants with different requirements. The application becomes universal by accepting modified identifiers that represent different tenants, enabling one application to perform multiple functions for different user groups while maintaining resource efficiency.
2Productivity
If multi-tenant technology is implemented to improve resource utilization, then system resource utilization is improved, but the complexity of managing tenant-specific identifiers deteriorates
Solution Approach 1:
A gateway or proxy component acts as an intermediary between users and the shared application. This intermediary automatically manages the mapping between original identifiers and modified identifiers, handling the complexity of tenant-specific routing without requiring changes to the application itself or increasing operational complexity.
Solution Approach 2:
Instead of managing complex tenant-specific configurations, the system creates simplified copies or representations of identifiers that can be easily modified. The modified identifiers serve as lightweight proxies that carry tenant information without replicating the full complexity of tenant management structures.
3Adaptability or versatility
If application source code is modified to support multi-tenancy, then tenant-specific functionality is improved, but ease of implementation deteriorates
Solution Approach 1:
The multi-tenancy management logic is extracted from the application source code and placed in an external component such as a gateway or configuration system. This separation allows the application to remain unchanged while still supporting multiple tenants, significantly improving ease of implementation while maintaining tenant-specific functionality through external identifier modification.
Data Source
AI summary
Implementations of the present specification provide a method and device for handling a multi-tenant request. A request to access an application from a user device is received, wherein the request includes a user identifier and request data. Tenant information corresponding to the user identifier is determined based on a mapping relationship between the user device and a tenant. Type information of the application is determined based on the request data. A first identifier of the application is extracted from the request data based on the type information of the application. The first identifier is modified to a second identifier based on the tenant information. A new request is determined based on the second identifier. The new request is sent to the application.