Multi-tenant Data Access via Isolated Schemas
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant cloud-based environments, existing solutions face challenges in efficiently managing access to isolated data sets organized using different application schemas, leading to complexities in data isolation and resource management across shared computing resources.
Innovation Solution
Implementing a multi-datastore architecture that allows multiple tenants to access different datastores using the same application code, where each datastore is organized using a customized application schema derived from a base schema, ensuring tenant isolation through unique application schemas and tenant identifiers, while allowing modifications to application schemas without affecting others.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a shared instance of server is created for multiple tenants with common application schema, then resource utilization is improved, but data isolation and schema customization capability deteriorate
Solution Approach 1:
The patent segments the data storage into separate datastores for each tenant while sharing the same application codebase. Each tenant has their own datastore with customized schema, enabling both resource sharing and schema customization. The segmentation is achieved through database-level isolation while maintaining application-level sharing.
Solution Approach 2:
The application code is designed to be universal and can access datastores from multiple tenants through a common interface. The same application code can serve multiple tenants with different schemas, achieving multi-functionality. This is enabled through abstraction layers that hide schema differences from the application layer.
2Reliability
If separate server instances are created for each tenant, then data isolation is improved, but resource utilization deteriorates
Solution Approach 1:
The patent merges multiple separate server instances into a single shared server that handles multiple tenants. Instead of creating separate physical or virtual servers for each tenant, the system uses a shared server with a unified architecture that provides data isolation through database-level segmentation rather than server-level separation.
Solution Approach 2:
An intermediary layer (abstraction layer) is introduced between the application code and the datastores. This intermediary manages the complexity of accessing different schemas and datastores, providing a unified interface that simplifies resource sharing while maintaining data isolation. The intermediary translates common application requests into tenant-specific schema operations.
3Adaptability or versatility
If application schema is customized for each tenant, then adaptability is improved, but system complexity deteriorates
Solution Approach 1:
The patent implements preliminary action by pre-defining a common base schema that all tenants inherit. Customizations are built upon this foundation rather than creating schemas from scratch. The base schema is established once and reused by all tenants, reducing the complexity of schema management while allowing individual customizations where needed.
Data Source
AI summary
Multi-tenant access to respective isolated data sets organized using different application schemas is disclosed. Multiple tenants store respective data sets in separate datastores. The datastores are organized using different application schemas, each derived from a same base schema. However, the tenants share access to a same application. The application receives a first request from a first tenant and a second request from a second tenant. The application serves the first request by accessing a first data set organized using a first application schema. The application serves the second request by accessing a second data set using a second application schema.