In-Memory Database Multi-Tenancy Schema Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional database management systems are inefficient in utilizing modern hardware capabilities, leading to performance bottlenecks due to disk access limitations, and managing multi-tenancy in software architectures is complex, especially when updating core software platforms or performing lifecycle management tasks across multiple tenants.
Innovation Solution
Implementing an in-memory database system with column-based storage, parallel execution capabilities, and distributed architecture that keeps all relevant data in main memory, minimizing CPU cache misses and disk operations, while allowing for tenant-specific configurations and secure data management across multiple tenants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional database management systems are used, then hardware resources can be utilized, but performance bottlenecks occur due to disk access limitations
Solution Approach 1:
The patent replaces the mechanical disk-based storage system with an in-memory database system. Data is stored in RAM rather than on disk, eliminating mechanical disk access operations. This substitution of the storage mechanism fundamentally resolves the performance bottleneck caused by disk access limitations, enabling faster data retrieval and processing.
Solution Approach 2:
The patent changes the storage parameter from disk-based to memory-based. By transitioning from traditional disk storage to in-memory storage, the system fundamentally alters the data access parameter, moving from sequential/disk-based access to immediate/random memory access, thereby eliminating the performance bottleneck.
2Adaptability or versatility
If multi-tenancy is implemented in software architecture, then resource sharing is enabled, but managing tenant-specific configurations becomes complex
Solution Approach 1:
The patent segments the database schema into common schema elements and tenant-specific schema extensions. This segmentation allows different tenants to have customized tables and fields while sharing a common base structure. The segmentation of schema management enables complex multi-tenancy to be handled through modular, manageable components rather than monolithic configuration.
Solution Approach 2:
The patent implements a nested schema structure where tenant-specific tables and fields are nested within or extended from common schema elements. This nesting approach allows tenant configurations to be organized hierarchically, with tenant-specific additions built upon the common foundation, making the complex configuration management more structured and manageable.
3Adaptability or versatility
If core software platform is updated, then new features are added, but lifecycle management tasks across multiple tenants become difficult
Solution Approach 1:
The patent implements a universal schema management mechanism that handles both common schema elements and tenant-specific extensions through a single unified approach. This multi-functional schema manager can process updates, additions, and modifications for all tenants simultaneously, enabling efficient lifecycle management across the multi-tenant environment without requiring separate management processes.
Solution Approach 2:
The patent uses schema copying mechanisms to propagate changes from the core software platform to tenant-specific schemas. When core platform updates are made, the schema manager creates and applies corresponding schema copies or extensions to each tenant's database structure, enabling efficient synchronization across all tenants during platform updates.
Data Source
AI summary
An in-memory database server hosting a tenant of a multi-tenant software architecture can receive a definition of a custom data field that is unique to an organization having isolated access to the tenant. The custom data field can extend a standard table defined by central metadata stored at a system tenant of the multi-tenant software architecture. Tenant private metadata that includes the definition can be stored in memory accessible only to the tenant. A tenant-dependent table that includes the custom data field can be formed, for example by retrieving central metadata defining the standard table from the system tenant and adding the custom data field using the definition. The tenant-dependent table can be presented for access via a database client at the organization. Related systems, articles of manufacture, and computer-implemented methods are disclosed.