Middleware Segmentation for Multi-Tenant Database Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional hosting solutions for multiple clients face challenges such as increased downtime during database upgrades, high manual effort for content deployment, and inefficiencies in backup and recovery processes due to shared database environments, which compromise data reliability and client autonomy.

Innovation Solution

Implementing a system where a provider hosts multiple tenants with shared and tenant-specific data structures, allowing each tenant to access their specific data while using standard database tools for management, ensuring isolation and independent management without affecting other tenants.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a multi-client system shares a common database for all clients, then resource utilization and scalability are improved, but database maintenance time and client downtime increase significantly

Engineering Contradiction:
Improveresource utilizationVSAvoiddatabase maintenance downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the common database into separate physical databases for each client. Each client's data is isolated in its own database instance, allowing independent maintenance, backup, and recovery operations. This segmentation enables the provider to perform database maintenance on one client's database without affecting other clients, thereby reducing overall maintenance downtime while maintaining resource efficiency through centralized management of multiple databases.

Inventive Principle:
Principle #1Segmentation

2Productivity

If a multi-client system uses a common database, then deployment efficiency is improved, but backup and recovery capability deteriorates

Engineering Contradiction:
Improvecontent deployment efficiencyVSAvoiddata backup and recovery reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

By creating separate physical databases for each client, the system enables use of standard database tools for backup and recovery operations on individual client databases. The provider can backup and recover specific client data independently without affecting other clients, significantly improving data reliability and recovery capability while maintaining efficient content deployment through centralized database management.

Inventive Principle:
Principle #1Segmentation

3Reliability

If a single-client system is used for each client, then data reliability and management independence are improved, but system complexity and client effort increase

Engineering Contradiction:
Improvedata management independenceVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements segmentation by providing each client with a separate physical database while maintaining centralized management infrastructure. This approach delivers the data independence and reliability of single-client systems, while the provider manages all databases through a unified platform, avoiding the operational complexity and client effort associated with fully distributed single-client deployments.

Inventive Principle:
Principle #1Segmentation

4Productivity

If client content is stored in a common database, then resource sharing is improved, but content deployment time and manual effort increase

Engineering Contradiction:
Improveresource sharing efficiencyVSAvoidcontent deployment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments client content into separate physical databases while maintaining centralized management capabilities. This structure enables efficient resource sharing through the management platform while allowing rapid content deployment to individual client databases without the need to sort through or lock other clients' content, significantly reducing deployment time and manual effort.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7739348B2Systems and methods for accessing a shared space in a provider-tenant environment by using middleware
Publication Date: 2010.06.15 SAP SE
  • US7739348B2 patent drawing
  • US7739348B2 patent drawing
  • US7739348B2 patent drawing

AI summary

The present invention discloses methods and systems for hosting tenants in a computer-based environment in which a provider stores a shared data structure. Each of the tenants may communicate with a middleware module storing metadata referencing the shared data structure and a tenant-specific data structure specific to the first tenant for access by the first tenant. Based on the metadata and in response to a data request from the first tenant, the system may the query the provider or the first tenant for requested data and provide the requested data based on the querying.