Multi-tenancy Wrapper for Non-Intrusive SaaS Enablement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for enabling multi-tenancy in software applications require costly and time-consuming re-architecting and reengineering, making it impractical for vendors to transition to an on-demand model without modifying existing code.
Innovation Solution
A non-intrusive approach utilizing existing security isolation capabilities and a wrapper interface that manages relationships between customers and data isolation mechanisms, allowing multi-tenancy without modifying the existing application code, and enabling seamless transition to a SaaS model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If re-architecting and reengineering is performed to enable multi-tenancy, then multi-tenancy capability is achieved, but development cost and time increase significantly
Solution Approach 1:
The patent introduces a multi-tenancy wrapper as an intermediary layer between the existing application and the multi-tenant environment. This wrapper sits on top of the application and provides multi-tenancy functionality without requiring modifications to the application's core code, thus avoiding time-consuming reengineering while achieving multi-tenancy capability.
Solution Approach 2:
The patent segments the multi-tenancy functionality into a separate wrapper component that can be independently deployed and managed. By separating the multi-tenancy logic from the application code, the system achieves multi-tenancy capability without requiring comprehensive reengineering of the entire application, significantly reducing development time.
2Adaptability or versatility
If re-architecting and reengineering is performed to enable multi-tenancy, then multi-tenancy capability is achieved, but development cost increases significantly
Solution Approach 1:
The multi-tenancy wrapper acts as a cost-effective intermediary that provides multi-tenancy functionality through a standardized interface. This approach eliminates the need for expensive custom reengineering of each application, as the wrapper can be applied uniformly across multiple applications with minimal customization.
Solution Approach 2:
The patent uses the existing application as a template and creates a multi-tenant version by adding the wrapper layer. This copying approach allows the same application to serve multiple tenants without the need to build separate applications or perform costly reengineering, significantly reducing development costs.
3Productivity
If existing security isolation capabilities are used with a wrapper, then rapid multi-tenancy enablement is achieved, but the application code must already have data isolation mechanism
Solution Approach 1:
The patent leverages the application's existing security isolation capabilities (such as user authentication and authorization mechanisms) to provide multi-tenancy. The wrapper utilizes these self-existing features without requiring the application to be modified, enabling rapid deployment while maintaining broad applicability to existing applications that already have basic security mechanisms.
Data Source
AI summary
A system for enabling non-intrusive multi tenancy enablement in an application may include a processing unit configured to, among other things, identify a data isolation mechanism available in said application, create a centralized multi-tenant database, generate a controlled provisioning layer to manage relationships between a set of consumers and a corresponding entity uniquely developed for said consumers, and generate a multi-tenant wrapper interface for managing relationship(s) between said consumers and instances of the application. The system may further include a memory unit configured to host said centralized customer database to manage users and associated access privileges in said application.