Hybrid Runtime Data Object for Multi-Tenant Reporting Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-tenant database systems face challenges in preventing the inadvertent intermingling of data from different entities during operations such as report generation, leading to data security and modeling issues.
Innovation Solution
A computing system that maintains multiple sets of data objects corresponding to multiple entities and reporting locations, and executes a hybrid class at runtime to generate a hybrid runtime data object with location-specific reporting data, ensuring data isolation by evaluating a mapping file to determine the source of reporting values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a multi-tenant database is used to store data of multiple entities, then storage efficiency and resource utilization are improved, but data security and isolation are worsened due to inadvertent intermingling of data from different entities
Solution Approach 1:
The patent segments the monolithic data object into multiple isolated data objects, each representing a specific entity. This segmentation prevents data intermingling while maintaining storage efficiency, as each entity's data is clearly demarcated and can be independently managed within the shared multi-tenant database structure.
Solution Approach 2:
The patent introduces an intermediary mechanism (the hybrid class with mapping file evaluation) that mediates between the shared database storage and the entity-specific data access. This intermediary ensures that data is retrieved from the correct entity context, preventing inadvertent intermingling while allowing efficient shared storage.
2Adaptability or versatility
If data from multiple entities is accessed during report generation, then reporting versatility is improved, but data isolation is worsened leading to modeling problems
Solution Approach 1:
The patent employs dynamic class instantiation where the hybrid class dynamically determines which entity-specific data objects to access based on the reporting context. This dynamic approach allows versatile reporting across multiple entities while maintaining clear data isolation, as the system adapts to the specific reporting needs without hardcoding complex data access patterns.
Solution Approach 2:
The patent changes the parameter of data object structure from a single monolithic object to multiple entity-specific objects with distinct parameters. This parameter change simplifies the data model by making entity boundaries explicit, reducing modeling complexity while enabling versatile reporting through systematic data access.
3Reliability
If a hybrid class with mapping file evaluation is implemented, then data isolation is improved, but processing time is worsened due to additional evaluation steps
Solution Approach 1:
The patent performs preliminary action by pre-establishing the mapping file that defines the relationship between hybrid class parameters and entity-specific data objects. This preliminary structuring allows for efficient runtime execution, as the system only needs to evaluate predefined mappings rather than making complex decisions during report generation, thus minimizing the time penalty.
4Reliability
If entity-specific data objects are maintained separately, then data security is improved, but system complexity is worsened due to multiple data object management
Solution Approach 1:
The patent applies universality by designing the hybrid class to work with multiple entity-specific data objects through a common interface and standardized parameter mapping. This multi-functional approach allows the same hybrid class structure to serve different entities, reducing system complexity despite maintaining separate data objects for security, as the management logic is unified rather than duplicated.
Data Source
AI summary
Methods, systems, devices, and tangible non-transitory computer readable media facilitating runtime reporting across multiple entities using a multi-tenant database including data of the multiple entities without intermingling the data. In an example embodiment, at a reporting runtime, the disclosed technology can: execute a hybrid class to generate a hybrid runtime data object that can include location-specific reporting data that can correspond to multiple entities and multiple reporting locations; evaluate, with respect to a certain reporting location, a mapping file of the hybrid class to determine whether to retrieve a reporting value of a reporting data field from a first data object corresponding to a first entity or from a second data object corresponding to a second entity; and/or access the first data object or the second data object to retrieve the reporting value based at least in part on evaluation of the mapping file.