Field Extensibility in Multi-Tenant Columnar Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant database environments, conventional methods for adding fields to database tables are not feasible as they can lead to conflicts and inconsistencies, and tenant isolation principles are compromised, making it difficult to customize systems to meet specific business process needs.
Innovation Solution
Implementing field extensibility by adding extension fields to business object nodes represented by tables in an in-memory, columnar database, with a one-to-one relationship between business object nodes and database tables, and using extension tables to persist these fields, while maintaining tenant isolation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If fields are added to database tables to meet customer customization needs, then adaptability is improved, but tenant isolation is compromised and conflicts arise
Solution Approach 1:
The patent segments the database schema into two distinct parts: a core schema that remains shared across all tenants and an extension schema that is customized per tenant. This is achieved by creating separate extension tables (e.g., CUSTOMER_EXTENSION_TABLE) that are logically separated from core tables (e.g., CUSTOMER_TABLE). Each tenant can define their own extension fields without affecting the core schema or other tenants, thus maintaining tenant isolation while enabling customization.
Solution Approach 2:
The patent introduces an intermediary layer in the form of extension tables that act as mediators between the core database schema and tenant-specific customization requirements. These extension tables serve as a buffer that allows tenants to add custom fields without directly modifying the core schema. The framework manages the integration between core and extension tables, ensuring that tenant-specific fields do not conflict with or expose information from other tenants.
2Ease of operation
If the database schema is modified to add custom fields, then ease of operation is improved, but system complexity increases
Solution Approach 1:
The patent establishes extension tables and frameworks in advance, before specific customization needs arise. The extension table structure, including primary keys, data types, and relationships with core tables, is pre-configured. This preliminary setup allows tenants to easily add custom fields later without requiring complex schema modifications, as the infrastructure for extensibility is already in place.
Solution Approach 2:
The extension table framework is designed to be universal and applicable to multiple tenants and different business scenarios. Rather than creating separate customization mechanisms for each tenant or scenario, the patent implements a single extensible framework that can accommodate various customization needs across all tenants. The extension tables use standard database constructs that work consistently throughout the system, reducing overall complexity.
Data Source
AI summary
A multi-tenant environment can support field extensibility via extension tables. An in-memory, columnar database can store a core table being extended as well as the corresponding extension table. Transactional and analytical processing can be performed on the extension fields. A business-objects-based system can take advantage of the technologies to provide greater flexibility, security, and performance improvements.