Multitenant Database Schema Replication for Cloud Data Isolation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data storage systems for cloud computing platforms struggle to efficiently isolate data between multiple tenants while maintaining security and efficiency, often requiring substantial modifications or wasteful infrastructure setups.

Innovation Solution

A database architecture that replicates the same schema for multiple tenants within a single database, using algorithmically generated object IDs based on tenant associations to ensure secure and efficient data access, allowing for the same schema to function similarly to a single-tenant environment without significant code modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate databases are used for each tenant to ensure data isolation, then security is improved, but infrastructure complexity and resource waste increase

Engineering Contradiction:

Improvedata isolation securityVSAvoidinfrastructure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the database schema into tenant-specific logical units using schema identifiers. Each tenant's data is isolated through schema-level separation while physically sharing the same database infrastructure. This allows maintaining security boundaries without creating separate physical databases for each tenant.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a universal database schema that can serve multiple tenants simultaneously. A single database instance with a standardized schema structure handles data for multiple tenants through parameterized queries and tenant context management, eliminating the need for tenant-specific database instances.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If separate databases are used for each tenant to ensure data isolation, then security is improved, but computing resource consumption increases

Engineering Contradiction:

Improvedata isolation securityVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple tenant databases into a single shared database instance. By combining storage resources and computational overhead into one database system while maintaining logical separation through schema identifiers, the solution reduces total resource consumption compared to maintaining separate database instances for each tenant.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent creates lightweight schema copies within the shared database for each tenant rather than duplicating entire database instances. These schema copies are minimal structural definitions that enable logical isolation without the full overhead of separate database systems.

Inventive Principle:

Principle #26Copying

3Ease of manufacture

If existing infrastructure is used without modifications to support multitenancy, then ease of deployment is improved, but data isolation capability deteriorates

Engineering Contradiction:

Improveease of deploymentVSAvoiddata isolation capability

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent incorporates multitenant capabilities into the database schema design from the beginning. Schema identifiers and tenant context management are built into the foundational structure, allowing multitenant deployment without requiring later modifications to existing infrastructure or applications.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses parameterized queries and dynamic schema identifier assignment to enable data isolation. By changing the parameter values (schema identifiers) based on tenant context, the same database infrastructure can securely serve multiple tenants with different data isolation requirements.

Inventive Principle:

Principle #35Parameter changes

4Adaptability or versatility

If schema replication is used for multiple tenants, then adaptability to multitenant environments is improved, but database complexity increases

Engineering Contradiction:

Improvemultitenant environment adaptabilityVSAvoiddatabase schema complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent replicates only the necessary schema elements needed for tenant isolation rather than duplicating entire database schemas. By applying partial replication to just the identification and isolation mechanisms, the solution achieves multitenant adaptability without proportionally increasing overall database complexity.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11003481B2System and method for an efficient and scalable multitenant database implementation for services platforms, including cloud services platforms

Publication Date: 2021.05.11 OPEN TEXT CORP

AI summary

Embodiments of a services application on web services platform that employs embodiments of a database architecture for use in multitenant environments that replicates the same schema in the context of a database are disclosed. These schemas can be accessed using a database access object corresponding to the database and a particular schema for a particular tenant. In particular, the object identifier used to access the objects of the schema may be algorithmically generated based on the tenant.