CN112995126A - Management method for supporting multiple data isolation strategies by multi-tenant platform - Google Patents
Management method for supporting multiple data isolation strategies by multi-tenant platform Download PDFInfo
- Publication number
- CN112995126A CN112995126A CN202110100077.6A CN202110100077A CN112995126A CN 112995126 A CN112995126 A CN 112995126A CN 202110100077 A CN202110100077 A CN 202110100077A CN 112995126 A CN112995126 A CN 112995126A
- Authority
- CN
- China
- Prior art keywords
- data
- tenant
- platform
- different
- data isolation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000002955 isolation Methods 0.000 title claims abstract description 110
- 238000007726 management method Methods 0.000 title claims abstract description 21
- 238000000034 method Methods 0.000 claims abstract description 19
- 238000013507 mapping Methods 0.000 claims description 4
- 238000012216 screening Methods 0.000 claims description 4
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 abstract description 5
- 208000035475 disorder Diseases 0.000 abstract description 5
- 101001072091 Homo sapiens ProSAAS Proteins 0.000 abstract 3
- 102100036366 ProSAAS Human genes 0.000 abstract 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
- H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Hardware Design (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a management method for supporting various data isolation strategies by a multi-tenant platform, relating to the technical field of SAAS platform multi-tenant; the problem that different tenants support different data isolation strategies under the same SAAS platform is solved; the method specifically comprises the following steps: the platform needs to store data isolation strategies and core information of different tenants; when a platform creates a tenant, the platform performs initialization operation according to different strategies; the data isolation strategy configuration of different tenants is stored in a tenant table with a unified platform; the data isolation policy includes a tenent _ id. The invention automatically performs switching, interception and rewriting operations according to the selected strategy every time of execution, supports different tenants to support the management and implementation scheme of different data isolation strategies under the same SAAS platform, realizes default division of tenant data, is transparent to a service layer, and reduces development cost and data disorder risk.
Description
Technical Field
The invention relates to the technical field of multiple tenants of an SAAS (software as a service) platform, in particular to a management method for supporting multiple data isolation strategies by a multiple-tenant platform.
Background
The multi-tenant technology realizes that hardware resources and software service capacity are provided for a plurality of tenants for use and are used as required without mutual influence, and one of key technologies for realizing the multi-tenant technology is a data isolation scheme. Because the service condition, data volume and load of each tenant are different, and the safety is also different, three typical data isolation strategies are provided according to the characteristic of multiple tenants of the SAAS platform. 1) Independent databases: a separate database is provided for each tenant, so that isolation on physical storage is performed, and the security and isolation level are best; 2) shared database, isolated data table: the same physical database can support a plurality of tenants, so that the management cost is reduced, and different tenants can perform defined data expansion; 3) shared database, shared data table: all tenants share one physical database and one data mode, one data table can have a plurality of tenant data, and the tenant data is generally distinguished through the tenant _ id.
Through retrieval, a patent with a Chinese patent application number of CN201710647616.1 discloses a multi-tenant isolation method and a device, and the isolation method comprises the following steps: a multi-tenant isolation method, the method comprising: receiving resource scheduling service requests of a plurality of tenants; the resource scheduling service request at least carries a service requested by a tenant and a service deployment node requested by the tenant; deploying n copies of the local data on a service deployment node of a tenant request needing the local data according to the resource scheduling service request and a target copy distribution strategy; and respectively deploying resource scheduling service strategies corresponding to the services requested by the tenants on the service deployment nodes requested by the tenants according to the resource scheduling service requests. The tenant isolation method and device for multiple tenants in the above patent have the following disadvantages: although the isolation of multiple tenants is realized, the data sharing among the multiple tenants is also realized, but no management and implementation scheme for supporting different tenants to support different data isolation strategies under the same SAAS platform is involved.
Disclosure of Invention
The invention aims to solve the defects in the prior art, and provides a management method for supporting multiple data isolation strategies by a multi-tenant platform.
In order to achieve the purpose, the invention adopts the following technical scheme:
a management method for supporting multiple data isolation strategies by a multi-tenant platform comprises the following steps:
s1: the platform needs to store data isolation strategies and core information of different tenants;
s2: when a platform creates a tenant, the platform performs initialization operation according to different strategies;
s3: and the data isolation strategy configuration of different tenants is stored in a tenant table unified by the platform.
Preferably: the data isolation policy comprises a tenant _ id, an isolation _ mode, a host and a database, wherein the isolation _ mode is a data isolation policy configured by a current tenant.
Preferably: the platform in S2 performs initialization operation according to different policies, and specifically includes the following steps:
s21: selecting a data isolation strategy and filling in necessary information when a tenant is created;
s22: creating a tenant schema, initializing a table structure and initializing table data.
Preferably: the operation of initializing the table data is realized through liquidbase third-party component management.
Preferably: the data isolation policy configuration of different tenants in S3 configures a data execution process stored in a tenant table unified by the platform, which specifically includes the following steps:
s51: dynamic data source loading: dynamically loading required data sources according to different tenant configurations;
s52: acquiring a data isolation strategy;
s53: intercepting a data source;
s54: intercepting the data table and routing to a physical table which really executes operation;
s55: and intercepting the data record.
Preferably: the data isolation policy acquisition step is specifically to acquire the data isolation policy configuration of the current tenant; the data source interception specifically comprises the steps of dynamically selecting a corresponding data source according to data isolation strategy configuration; and the data record interception supports sharing the data table and SQL rewriting is carried out.
Preferably: the data isolation policy configuration of different tenants in S3 includes a saving and dynamic loading mechanism for different configurations, and corresponding policy attributes are saved according to different data isolation policies.
Preferably: the initial tenant initialization scheme according to different data isolation strategies comprises the following steps:
s61: dynamically loading different data sources according to the configuration of all tenants;
s62: and finishing hot loading in the process of newly adding the data source.
Preferably: according to the unified implementation scheme of the different data isolation strategies, the service application layer does not need to care about the data isolation strategies and focuses on the implementation of the service function of the service application layer.
Preferably: the unified implementation scheme of the different data isolation strategies performs switching, intercepting and rewriting operations automatically according to the selected strategy every time of execution, and specifically comprises the following steps:
s71: automatically switching a database corresponding to a tenant of the current request;
s72: automatically mapping to a data table corresponding to the tenant of the current request;
s73: and automatically adding data screening conditions of the tenants.
The invention has the beneficial effects that:
1. the invention automatically performs switching, interception and rewriting operations according to the selected strategy every time of execution, supports different tenants to support the management and implementation scheme of different data isolation strategies under the same SAAS platform, realizes default division of tenant data, is transparent to a service layer, and reduces development cost and data disorder risk.
2. According to the invention, by storing the data isolation strategies of a plurality of tenants, the platform performs initialization operation according to different strategies, the data isolation strategy configuration of different tenants is stored in a unified tenant table of the platform, corresponding strategy attributes are stored according to different data isolation strategies, and different data sources are dynamically loaded.
3. The business application layer does not need to care about a data isolation strategy, focuses on realizing the business function of the business application layer, realizes the isolation of resources, fully utilizes the existing resources, does not increase the platform management cost budget, and ensures the safety of tenant data storage in the database.
Drawings
Fig. 1 is a schematic flowchart of a management method for supporting multiple data isolation policies by a multi-tenant platform according to the present invention;
fig. 2 is a schematic diagram of a data execution flow of data isolation policy configuration of different tenants stored in a tenant table unified by a platform according to a management method for a multi-tenant platform supporting multiple data isolation policies provided by the present invention.
Detailed Description
The technical solution of the present patent will be described in further detail with reference to the following embodiments.
Reference will now be made in detail to embodiments of the present patent, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present patent and are not to be construed as limiting the present patent.
In the description of this patent, it is to be understood that the terms "center," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like are used in the orientations and positional relationships indicated in the drawings for the convenience of describing the patent and for the simplicity of description, and are not intended to indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and are not to be considered limiting of the patent.
In the description of this patent, it is noted that unless otherwise specifically stated or limited, the terms "mounted," "connected," and "disposed" are to be construed broadly and can include, for example, fixedly connected, disposed, detachably connected, disposed, or integrally connected and disposed. The specific meaning of the above terms in this patent may be understood by those of ordinary skill in the art as appropriate.
Example 1:
a management method for a multi-tenant platform to support multiple data isolation policies, as shown in fig. 1 and fig. 2, includes the following steps:
s1: the platform needs to store data isolation strategies and core information of different tenants;
s2: when a platform creates a tenant, the platform performs initialization operation according to different strategies;
s3: and the data isolation strategy configuration of different tenants is stored in a tenant table unified by the platform.
The data isolation policy comprises a tenant _ id, an isolation _ mode, a host and a database, wherein the isolation _ mode is a data isolation policy configured by a current tenant.
The platform in S2 performs initialization operation according to different policies, and specifically includes the following steps:
s21: selecting a data isolation strategy and filling in necessary information when a tenant is created;
s22: creating a tenant schema, initializing a table structure and initializing table data.
Further, the operation of initializing the table data may be implemented through third-party component management such as liquidbase.
The data isolation policy configuration of different tenants in S3 configures a data execution process stored in a tenant table unified by the platform, which specifically includes the following steps:
s51: dynamic data source loading: dynamically loading required data sources according to different tenant configurations;
s52: acquiring a data isolation strategy;
s53: intercepting a data source;
s54: intercepting the data table and routing to a physical table which really executes operation;
s55: and intercepting the data record.
Further, the obtaining of the data isolation policy is specifically obtaining of a data isolation policy configuration of a current tenant.
Further, the data source interception specifically is to dynamically select a corresponding data source according to the data isolation policy configuration.
Furthermore, the data record interception supports sharing of the data table, SQL rewriting is carried out, a tenth _ id condition is newly added in the SQL, default distinguishing of tenant data is achieved, a service layer is transparent, and development cost and data disorder risk are reduced.
The data isolation policy configuration of different tenants in S3 includes a saving and dynamic loading mechanism for different configurations, and corresponding policy attributes are saved according to different data isolation policies.
Further, the initial tenant initialization scheme according to different data isolation policies includes the following steps:
s61: dynamically loading different data sources according to the configuration of all tenants;
s62: in the process of adding a new data source, hot loading can be completed.
Further, according to the unified implementation scheme of the different data isolation strategies, the service application layer does not need to concern about the data isolation strategies and focuses on the implementation of the service functions of the service application layer.
Further, the unified implementation scheme of the different data isolation policies performs switching, intercepting and rewriting operations automatically according to the selected policy every time the unified implementation scheme is executed, and specifically includes the following steps:
s71: automatically switching a database corresponding to a tenant of the current request;
s72: automatically mapping to a data table corresponding to the tenant of the current request;
s73: and automatically adding data screening conditions of the tenants.
When the system is used, data isolation strategies of a plurality of tenants are stored, the platform performs initialization operation according to different strategies, the data isolation strategies of different tenants are configured and stored in a tenant table unified by the platform, corresponding strategy attributes are stored according to different data isolation strategies, different data sources are dynamically loaded, and switching, intercepting and rewriting operations are automatically performed each time according to a selected strategy, management and implementation schemes that different tenants support different data isolation strategies are supported under the same SAAS platform, default division of tenant data is realized, business layers are transparent, and development cost and data disorder risk are reduced.
Example 2:
a management method for a multi-tenant platform to support multiple data isolation policies, as shown in fig. 1 and fig. 2, includes the following steps:
s1: the platform needs to store data isolation strategies and core information of different tenants;
s2: when a platform creates a tenant, the platform performs initialization operation according to different strategies;
s3: and the data isolation strategy configuration of different tenants is stored in a tenant table unified by the platform.
The data isolation policy comprises a tenant _ id, an isolation _ mode, a host and a database, wherein the isolation _ mode is a data isolation policy configured by a current tenant.
The platform in S2 performs initialization operations according to different policies, specifically including selecting a data isolation policy and filling in necessary information when creating a tenant.
Further, the operation of initializing the table data may be implemented through third-party component management such as liquidbase.
The data isolation policy configuration of different tenants in S3 configures a data execution process stored in a tenant table unified by the platform, which specifically includes the following steps:
s51: dynamic data source loading: dynamically loading required data sources according to different tenant configurations;
s52: acquiring a data isolation strategy;
s53: intercepting a data source;
s54: intercepting the data table and routing to a physical table which really executes operation;
s55: and intercepting the data record.
Further, the obtaining of the data isolation policy is specifically obtaining of a data isolation policy configuration of a current tenant.
Further, the data source interception specifically is to dynamically select a corresponding data source according to the data isolation policy configuration.
Furthermore, the data record interception supports sharing of the data table, SQL rewriting is carried out, a tenth _ id condition is newly added in the SQL, default distinguishing of tenant data is achieved, a service layer is transparent, and development cost and data disorder risk are reduced.
The data isolation policy configuration of different tenants in S3 includes a saving and dynamic loading mechanism for different configurations, and corresponding policy attributes are saved according to different data isolation policies.
Further, the initial tenant initialization scheme according to different data isolation policies includes the following steps:
s61: dynamically loading different data sources according to the configuration of all tenants;
s62: in the process of adding a new data source, hot loading can be completed.
Further, according to the unified implementation scheme of the different data isolation strategies, the service application layer does not need to concern about the data isolation strategies and focuses on the implementation of the service functions of the service application layer.
Further, the unified implementation scheme of the different data isolation policies performs switching, intercepting and rewriting operations automatically according to the selected policy every time the unified implementation scheme is executed, and specifically includes the following steps:
s71: automatically switching a database corresponding to a tenant of the current request;
s72: automatically mapping to a data table corresponding to the tenant of the current request;
s73: and automatically adding data screening conditions of the tenants.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art should be considered to be within the technical scope of the present invention, and the technical solutions and the inventive concepts thereof according to the present invention should be equivalent or changed within the scope of the present invention.
Claims (10)
1. A management method for supporting multiple data isolation strategies by a multi-tenant platform is characterized by comprising the following steps:
s1: the platform needs to store data isolation strategies and core information of different tenants;
s2: when a platform creates a tenant, the platform performs initialization operation according to different strategies;
s3: and the data isolation strategy configuration of different tenants is stored in a tenant table unified by the platform.
2. The method as claimed in claim 1, wherein the data isolation policy includes a tenant _ id, an isolation _ mode, a host, and a database, and the isolation _ mode is a data isolation policy configured by a current tenant.
3. The method according to claim 2, wherein the platform in S2 performs initialization according to different policies, and specifically includes the following steps:
s21: selecting a data isolation strategy and filling in necessary information when a tenant is created;
s22: creating a tenant schema, initializing a table structure and initializing table data.
4. The method for managing multiple data isolation policies supported by a multi-tenant platform according to claim 3, wherein the operation of initializing table data is implemented by liquidbase third-party component management.
5. The method according to claim 4, wherein the data isolation policy configuration of different tenants in S3 configures a data execution process stored in a tenant table unified by the platform, and specifically includes the following steps:
s51: dynamic data source loading: dynamically loading required data sources according to different tenant configurations;
s52: acquiring a data isolation strategy;
s53: intercepting a data source;
s54: intercepting the data table and routing to a physical table which really executes operation;
s55: and intercepting the data record.
6. The method according to claim 5, wherein the data isolation policy acquisition policy is specifically configured to acquire a data isolation policy of a current tenant; the data source interception specifically comprises the steps of dynamically selecting a corresponding data source according to data isolation strategy configuration; and the data record interception supports sharing the data table and SQL rewriting is carried out.
7. The method as claimed in claim 1, wherein the data isolation policy configuration of different tenants in S3 includes a saving and dynamic loading mechanism for different configurations, and the policy attributes are saved according to different data isolation policies.
8. The method according to claim 7, wherein the initial tenant initialization scheme according to different data isolation policies comprises the following steps:
s61: dynamically loading different data sources according to the configuration of all tenants;
s62: and finishing hot loading in the process of newly adding the data source.
9. The method according to claim 8, wherein the business application layer does not need to care about the data isolation policy and focuses on the implementation of the business function of the business application layer.
10. The method for managing a multi-tenant platform supporting multiple data isolation policies according to any one of claims 1 to 9, wherein a unified implementation scheme of the different data isolation policies automatically performs switching, intercepting, and rewriting operations according to a selected policy each time the unified implementation scheme is executed, and specifically includes the following steps:
s71: automatically switching a database corresponding to a tenant of the current request;
s72: automatically mapping to a data table corresponding to the tenant of the current request;
s73: and automatically adding data screening conditions of the tenants.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110100077.6A CN112995126A (en) | 2021-01-25 | 2021-01-25 | Management method for supporting multiple data isolation strategies by multi-tenant platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110100077.6A CN112995126A (en) | 2021-01-25 | 2021-01-25 | Management method for supporting multiple data isolation strategies by multi-tenant platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112995126A true CN112995126A (en) | 2021-06-18 |
Family
ID=76345403
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110100077.6A Pending CN112995126A (en) | 2021-01-25 | 2021-01-25 | Management method for supporting multiple data isolation strategies by multi-tenant platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112995126A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115391828A (en) * | 2022-10-31 | 2022-11-25 | 泰豪软件股份有限公司 | Data isolation method and system of multi-tenant platform based on micro-service architecture |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101408899A (en) * | 2008-11-21 | 2009-04-15 | 北京中企开源信息技术有限公司 | Method and apparatus for switching website multiple data sources |
| CN101777047A (en) * | 2009-01-08 | 2010-07-14 | 国际商业机器公司 | System, equipment and method for accessing database under multiple-tenant environment |
| US20110270886A1 (en) * | 2010-04-30 | 2011-11-03 | International Business Machines Corporation | Mechanism and apparatus for transparently enables multi-tenant file access operation |
| CN102456028A (en) * | 2010-10-27 | 2012-05-16 | 金蝶软件（中国）有限公司 | Multi-tenant-oriented data acquisition method, device and system |
| CN108520004A (en) * | 2018-03-12 | 2018-09-11 | 舟谱数据技术南京有限公司 | Based on method parameter section multi-tenant data source switching system |
| CN109241028A (en) * | 2018-08-02 | 2019-01-18 | 山东浪潮通软信息科技有限公司 | A kind of database multi-tenant implementation method based on Mycat |
| US20190130121A1 (en) * | 2017-10-26 | 2019-05-02 | Sap Se | System sharing types in multi-tenancy database systems |
| CN111582773A (en) * | 2020-06-22 | 2020-08-25 | 南京德睿能源研究院有限公司 | Multi-tenant technology-based micro-grid energy cloud model control method and system |
| CN112200635A (en) * | 2020-10-21 | 2021-01-08 | 中国电子科技集团公司第十五研究所 | Multi-tenant data isolation method and system based on tenant attributes |
-
2021
- 2021-01-25 CN CN202110100077.6A patent/CN112995126A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101408899A (en) * | 2008-11-21 | 2009-04-15 | 北京中企开源信息技术有限公司 | Method and apparatus for switching website multiple data sources |
| CN101777047A (en) * | 2009-01-08 | 2010-07-14 | 国际商业机器公司 | System, equipment and method for accessing database under multiple-tenant environment |
| US20110270886A1 (en) * | 2010-04-30 | 2011-11-03 | International Business Machines Corporation | Mechanism and apparatus for transparently enables multi-tenant file access operation |
| CN102456028A (en) * | 2010-10-27 | 2012-05-16 | 金蝶软件（中国）有限公司 | Multi-tenant-oriented data acquisition method, device and system |
| US20190130121A1 (en) * | 2017-10-26 | 2019-05-02 | Sap Se | System sharing types in multi-tenancy database systems |
| CN108520004A (en) * | 2018-03-12 | 2018-09-11 | 舟谱数据技术南京有限公司 | Based on method parameter section multi-tenant data source switching system |
| CN109241028A (en) * | 2018-08-02 | 2019-01-18 | 山东浪潮通软信息科技有限公司 | A kind of database multi-tenant implementation method based on Mycat |
| CN111582773A (en) * | 2020-06-22 | 2020-08-25 | 南京德睿能源研究院有限公司 | Multi-tenant technology-based micro-grid energy cloud model control method and system |
| CN112200635A (en) * | 2020-10-21 | 2021-01-08 | 中国电子科技集团公司第十五研究所 | Multi-tenant data isolation method and system based on tenant attributes |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115391828A (en) * | 2022-10-31 | 2022-11-25 | 泰豪软件股份有限公司 | Data isolation method and system of multi-tenant platform based on micro-service architecture |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11979285B2 (en) | System and method for generic configuration management system application programming interface | |
| CN103226561B (en) | Content addressable storage based on brother's group | |
| US20210064442A1 (en) | Implementing An Application Manifest In A Node-Specific Manner Using An Intent-Based Orchestrator | |
| US9542432B2 (en) | Systems and methods for multitenancy data | |
| US5287500A (en) | System for allocating storage spaces based upon required and optional service attributes having assigned piorities | |
| US20100030995A1 (en) | Method and apparatus for applying database partitioning in a multi-tenancy scenario | |
| US9342572B2 (en) | Workflow processing system and method with database system support | |
| US20050114611A1 (en) | Computerized system, method and program product for managing an enterprise storage system | |
| CN111582773B (en) | Multi-tenant technology-based micro-grid energy cloud model control method and system | |
| US7467166B2 (en) | System and method for heterogeneous caching | |
| JPWO2013161080A1 (en) | Database management system, computer, database management method | |
| US20220075757A1 (en) | Data read method, data write method, and server | |
| US20030105840A1 (en) | Method and apparatus for managing configuration information in a distributed computer system | |
| AU2017440072B2 (en) | Network entity and method for identifier allocating and/or identifier mapping of network services | |
| US20130239004A1 (en) | System and method for providing an in-memory data grid application container | |
| CN113190529A (en) | Multi-tenant data sharing storage system suitable for MongoDB database | |
| CN106686140A (en) | Network virtualization storage method, equipment and system | |
| US20230384959A1 (en) | Capacity expansion method and system for a storage cluster, and related device | |
| US8443369B1 (en) | Method and system for dynamically selecting a best resource from each resource collection based on resources dependencies, prior selections and statistics to implement an allocation policy | |
| CN112995126A (en) | Management method for supporting multiple data isolation strategies by multi-tenant platform | |
| CN103106242A (en) | Phone bill query method and phone bill query system | |
| US9361351B2 (en) | Data management via active and inactive table space containers | |
| US8108523B2 (en) | Automatic extension of distributed managed ranges in a multi-master system | |
| CN105354319B (en) | For the database connection pool management method and system of the MPP data-base cluster of SN framework | |
| US20130219364A1 (en) | Systems and methods for assigning code lines to clusters with storage and other constraints |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |