Multitenant Content Server Partitioned Database Architecture

Solution Overview

Problem

Existing content management systems deployed on cloud-based platforms face challenges in supporting multitenancy, leading to high costs, slow deployment times, and increased administrative overhead due to the need for separate instances and resources for each tenant, which compromises security and efficiency.

Innovation Solution

A multitenant content management system utilizing a partitioned database with a global partition for shared common data and tenant-specific partitions, allowing for dynamic creation and management of tenant partitions, ensuring data isolation and security while optimizing resource usage and deployment speed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate content management server instances are deployed for each tenant, then data isolation and security are improved, but device complexity and deployment costs increase

Engineering Contradiction:

Improvedata isolationVSAvoiddeployment complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The database is segmented into separate schemas for each tenant within a single content management server instance. Each tenant's data is isolated in its own database schema, providing data isolation and security while avoiding the complexity of deploying separate server instances for each tenant. This allows the system to maintain security boundaries without replicating entire server infrastructure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A single content management server instance is designed to serve multiple tenants simultaneously by dynamically routing requests to the appropriate database schema based on tenant identification. The server performs multiple functions (servicing different tenants) within a unified architecture, reducing deployment complexity while maintaining data isolation through schema-based separation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If separate content management server instances are deployed for each tenant, then data security is improved, but productivity and deployment speed decrease

Engineering Contradiction:

Improvedata securityVSAvoiddeployment speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The database is segmented into separate schemas for each tenant within a single content management server instance. Each tenant's data is isolated in its own database schema, providing data isolation and security while avoiding the complexity of deploying separate server instances for each tenant. This allows the system to maintain security boundaries without replicating entire server infrastructure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system establishes tenant identification and database schema mapping mechanisms in advance, allowing new tenants to be onboarded quickly by simply creating their database schema and registering their identifier, rather than deploying an entire server instance. This preliminary setup enables rapid provisioning while maintaining security.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If separate content management server instances are deployed for each tenant, then data isolation is improved, but use of computational resources increases

Engineering Contradiction:

Improvedata isolationVSAvoidcomputational resource usage

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Multiple tenant environments are merged into a single content management server instance with a unified database system. The database is organized with separate schemas for each tenant, allowing data isolation while sharing the underlying computational resources (CPU, memory, storage) of the single server instance. This reduces total resource consumption compared to running separate instances for each tenant.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The database is segmented into separate schemas for each tenant within a single content management server instance. Each tenant's data is isolated in its own database schema, providing data isolation and security while avoiding the complexity of deploying separate server instances for each tenant. This allows the system to maintain security boundaries without replicating entire server infrastructure.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12153966B2System and method for an efficient and scalable multitenant implementation for content management services platforms, including cloud deployed content management services platforms

Publication Date: 2024.11.26 OPEN TEXT HOLDINGS INC

AI summary

Embodiments of a multitenant content server that employs embodiments of a database architecture for use in multitenant environments that include a global partition and a tenant partition for each tenant. These partitions can be accessed using sessions corresponding to the partitions and interfaces associated with the tenants.