Unified Interface for Hybrid Datastore Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant, cloud-based environments, existing systems face challenges in seamlessly accessing and managing on-premise and off-premise datastores that use different application schemas, leading to complexities in data retrieval and integration across disparate systems.
Innovation Solution
A single interface is implemented to serve requests from tenants by selectively accessing either on-premise or off-premise datastores based on the request, without specifying the datastore, allowing for partial data migration and maintaining isolation between tenants' data sets using tenant identifiers and application schemas.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate instances of servers are created for each tenant with separate application code and schema, then data isolation between tenants is improved, but device complexity increases
Solution Approach 1:
The patent segments the application schema by creating separate schema instances for on-premise and off-premise datastores, while maintaining a shared server instance. This allows data isolation through schema separation without requiring complete system segmentation, thus reducing device complexity while preserving reliability.
Solution Approach 2:
The patent introduces an intermediary layer (the interface) that mediates between tenants and the shared server instance. This interface manages the complexity of accessing different datastores with different schemas, allowing the server to remain shared while maintaining data isolation through controlled access mechanisms.
2Device complexity
If a shared instance of server is created for multiple tenants with common application schema, then device complexity is reduced, but adaptability to different application schemas worsens
Solution Approach 1:
The shared server instance is designed with multi-functionality to serve multiple tenants with different application schemas. The interface layer provides universal access mechanisms that can handle both on-premise and off-premise datastores, allowing the single server to adapt to various schema requirements without requiring separate instances.
Solution Approach 2:
The system dynamically selects which datastore (on-premise or off-premise) to access based on the specific tenant and application schema requirements. This dynamic adaptation allows the shared server instance to flexibly serve different schema types without being constrained to a single schema structure.
3Ease of operation
If data sets are migrated fully to off-premise environment, then integration with cloud-based applications is improved, but loss of time and resources increases
Solution Approach 1:
Instead of performing complete data migration, the patent applies partial action by allowing selective access to on-premise datastores when needed. The interface enables cloud-based applications to access data from either on-premise or off-premise locations based on specific requirements, avoiding the time-consuming process of full migration while still achieving cloud integration benefits.
Solution Approach 2:
The interface acts as an intermediary that enables cloud-based applications to access on-premise datastores without requiring physical data migration. This mediator layer provides seamless access to both on-premise and off-premise data, eliminating migration time while maintaining integration capabilities.
4Adaptability or versatility
If multiple interfaces are created to access on-premise and off-premise datastores, then adaptability to different environments is improved, but device complexity increases
Solution Approach 1:
The patent implements a single universal interface that can access both on-premise and off-premise datastores. This multi-functional interface eliminates the need for separate interfaces for different environments, maintaining adaptability while reducing interface complexity through consolidation.
Solution Approach 2:
The patent merges the functionality of multiple potential interfaces (on-premise interface and off-premise interface) into a single unified interface. This combining approach maintains the ability to access different datastore types while reducing overall interface complexity by eliminating redundant access mechanisms.
Data Source
AI summary
Techniques are disclosed for accessing on-premise and off-premise datastores organized using different application schemas. An interface serves requests, from a tenant, by accessing either the on-premise datastore or the off-premise datastore. The interface receives a request for a particular data set. Based on the request itself, the interface selects either the on-premise datastore or the off-premise datastore to retrieve the particular data set. The interface retrieves the particular data set from the selected datastore without attempting to retrieve the particular data set from the non-selected datastore. The interface transmits and/or presents the particular data set.