CN104462421B - Multi-tenant extended method based on key-value database - Google Patents

Abstract

The embodiment of the present invention relates to a multi-tenant extension method based on a key-value database. The method includes: acquiring metadata of an initial business entity; Attributes define business entities and display labels, and generate specific business entity metadata that meets multi-tenant requirements; in the instance generation phase, create a key-value Key-Value database based on the specific business entity metadata; in the instance running phase, the tenant ID is used as The RowKey prefix is inserted into the business entity data of the Key-Value database, and the business entity data is queried within the query range of the RowKey generated by the tenant ID, and the business entity data is taken out from the Key-Value database within the query range, according to the The specific business entity metadata generates an interactive interface for displaying the business entity data.

Description

Multi-tenant extension method based on key-value database

technical field

The invention relates to the computer field, in particular to a multi-tenant extension method based on a key-value database.

Background technique

The rapid development of Internet technology has made traditional databases face huge challenges in dealing with massive data. Distributed key-value Key-Value databases have emerged as the times require. Key-Value databases include open source non-relational distributed database HBase, non-relational database Cassandra , Non-relational databases, SQL, etc. Compared with the traditional relational database, the distributed architecture of the Key-Value database can store a large amount of data, and a table can have hundreds of millions of rows; column-oriented storage, column (family)-oriented storage and permission control, column (family) independent retrieval; Sparse storage, for empty columns, no storage space is occupied, and the table can be designed very sparsely.

Multi-tenant technology is mainly used for multiple tenants to share hardware resources, and multiple tenants share one application instance. In the prior art, multi-tenant technology mainly includes the following three solutions in terms of data storage:

1. Each tenant has an independent database

Provide independent databases for different tenants, so that the data isolation is the best, and because the database structure can be designed separately for different users, it helps to simplify the design of the database structure, and the failure recovery is relatively simple. However, if an independent database is established for each tenant, different tenants do not really share hardware resources, and the acquisition and maintenance costs are high, which is generally unacceptable to operators.

2. Tenants share the database, but have independent database tables

All tenants share a database, but different tenants have independent database tables. It provides a certain isolation between data, but it is relatively cumbersome to expand, not easy to expand, and the cost is high, and cross-tenant data statistics are difficult.

3. Tenants share the database and share the database table

All tenants share the database and shared database tables. This method has the lowest cost, the highest degree of sharing, and the most supported tenants. However, due to the different business needs of different tenants, the database needs to be carefully designed for this situation. When using a traditional relational database, when a tenant needs to add a custom field, it needs to add a column in the database. For a tenant, the columns added by other tenants are useless columns for the tenant, but they still need to exist in the database, but When the number of tenants is large, a large number of columns need to be added to the database, which leads to a large number of null values in the database, which is a waste of space.

Contents of the invention

The embodiment of the present invention provides a multi-tenant expansion method based on a key-value database, which can effectively reduce the operation cost and maintenance cost of the multi-tenant database, increase the scalability of the multi-tenant database, reduce the customization cost of tenants and shorten the customization cycle.

An embodiment of the present invention provides a multi-tenant extension method based on a key-value database, the method comprising:

Get initial business entity metadata;

In the customization stage, business attributes are extended on the initial business entity metadata, business entities and display labels are defined for the business attributes, and specific business entity metadata meeting multi-tenant requirements are generated;

In the instance generation phase, a key-value Key-Value database is created according to the metadata of the specific business entity;

In the instance running phase, the business entity data is inserted into the Key-Value database with the tenant ID as the RowKey prefix, and the business entity data is queried within the query range of the RowKey generated by the tenant ID, and the Key-Value database is retrieved within the query range The business entity data is taken out, and an interactive interface is generated according to the specific business entity metadata, so as to display the business entity data.

Preferably, both the initial business entity metadata and the specific business entity metadata include at least: the table name of the business entity, the display label of the business entity, the attribute column name of the business entity, the data type of the business entity, the Indexed column IDs and properties of business entities display labels.

Preferably, in the stage of generating an instance, the method further includes:

All tenants share one Key-Value database, and the column corresponding to the initial business entity metadata is shared by all tenants.

Preferably, in the stage of generating an instance, the method further includes:

The extended service attributes are used to meet the different service requirements of the tenants, and at the same time, an extended column corresponding to the newly added service attribute is generated, and the extended column is only visible to the tenant.

Preferably, inserting the business entity data into the Key-Value database with the tenant ID as the RowKey prefix specifically further includes: using the tenant ID + the business entity table name as the RowKey prefix of the business entity data.

Preferably, the querying service entity data by generating the query scope of the RowKey generated by the tenant identifier specifically includes: querying the Key-Value database, setting the query scope according to the tenant identifier and the table name of the service entity, in Within the set query range, query is performed according to the query conditions set by the user to obtain the business entity data.

Preferably, the generating the interactive interface according to the metadata of the specific business entity specifically includes:

Obtaining the specific business entity metadata of the tenant according to the identifier of the tenant;

generating query items according to the index column information and data types of the tenant's specific business entity metadata;

displaying query results according to display tags and business entity data in the tenant-specific business entity metadata;

The new item of the new page is generated according to the display label of the business entity, the attribute display label of the business entity, and the data type of the business entity in the metadata of the specific business entity of the tenant.

The multi-tenant expansion method based on the key-value database proposed by the present invention can produce positive beneficial effects, specifically as follows: it supports the generation of applications that meet the individual needs of tenants through customization, and can avoid repeated development for services with similar business processes; The Key-Value database is convenient for expansion and reduces operating costs. With the growth of new tenants and the growth of the user scale of tenants, the present invention uses the tenant identifier as the RowKey prefix of all business entity data to facilitate expansion and reduce operating costs.

Description of drawings

FIG. 1 is a flowchart of a multi-tenant extension method based on a key-value database provided in Embodiment 1 of the present invention;

FIG. 2 is a functional block diagram of a key-value database-based multi-tenant extension method provided by Embodiment 2 of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the specific embodiments of the present invention will be further described in detail below in conjunction with the accompanying drawings.

Embodiment one

The following uses Figure 1 as an example to describe in detail the multi-tenant extension method based on the key-value database provided by Embodiment 1 of the present invention. Figure 1 is a flowchart of the multi-tenant extension method based on the key-value database provided by the embodiment of the present invention. The implementation subject in the embodiment of the invention may be an operation support platform. FIG. 2 shows a functional block diagram of a key-value database-based multi-tenant extension method proposed by an embodiment of the present invention. As shown in Figure 2, in the multi-tenant expansion method based on the key-value database proposed by the present invention, an expandable and definable multi-tenant operation support platform is adopted, and the platform uses a distributed Key-Value database to store business information. As shown in Figure 1 and Figure 2, the method includes the following steps:

Step 101, obtaining initial business entity metadata;

The initial business entity metadata includes at least: the table name of the business entity, the display label of the business entity, the attribute column name of the business entity, the data type of the business entity, the index column identifier of the business entity, and the attribute display label of the business entity.

Step 102, customization phase, extend business attributes on the initial business entity metadata, define business entities and display labels for the business attributes, and generate specific business entity metadata that meets multi-tenant requirements.

Both the initial business entity metadata and the specific business entity metadata include at least: the table name of the business entity, the display label of the business entity, the attribute column name of the business entity, the data type of the business entity, and the index column identifier of the business entity and attributes of business entities display labels.

Specifically, before the deployment of the operation support platform, the initial business entity metadata of each module is formulated according to the business requirements of each module, and the Key-Value database table is created according to the initial business metadata. For example, the business metadata structure is mainly shown in Table 1 :

Table 1 Business metadata structure table

Create the database table CRM structure according to the template as shown in Table 2:

Table 2 Database table CRM structure table

Step 103 , in the stage of generating an instance, a key-value Key-Value database is created according to the metadata of the specific business entity.

During the generating instance phase, the method further includes:

All tenants share one Key-Value database, and the column corresponding to the initial business entity metadata is shared by all tenants.

Specifically, in the customization phase, the tenant customizes the initial business entity metadata based on domain knowledge based on the initial business entity metadata, and generates tenant-specific business entity metadata by modifying the initial column information and adding custom column information.

Tenant 1 is an educational institution. According to business requirements, the entity name corresponding to CRM is changed to "student"; the attribute label corresponding to the "USER_NAME" column in the initial business entity metadata is changed to "student name", and the corresponding attribute of "USER_ID" Change the label to "student number"; add the attribute "grade" to the business entity "student", and define the corresponding custom column. Through the above customization, tenant 1 generates the metadata of the custom business entity, as shown in Table 3:

Table 3 Custom business entity metadata generated by tenant 1

Tenant 2 is a company user. According to business requirements, change the entity name corresponding to CRM to "employee"; the attribute label corresponding to the "USER_NAME" column in the initial business entity metadata is changed to "employee name", and the corresponding attribute of "USER_ID" Change the label to "employee number"; add the attribute "department" to the business entity "employee", and define the corresponding custom column. Through the above customization, tenant 2 generates the metadata of the custom business entity, as shown in Table 4:

Table 4 Custom business entity metadata generated by tenant 2

According to the custom business entity metadata generated by tenant 1 and tenant 2, we can define several similar custom business entity metadata. Similarly, we assume that tenant N is a management personnel of an enterprise, and according to business needs, the entity corresponding to CRM The name is changed to "manager"; the attribute label corresponding to the "USER_NAME" column in the initial business entity metadata is changed to "administrator", and the attribute label corresponding to "USER_ID" is changed to "administrator number"; the business entity "employee" is added Attribute "department" and define the corresponding custom columns. Through the above customization, tenant N generates custom business entity metadata as shown in Table 5:

Table 5 Custom business entity metadata generated by tenant N

During the generating instance phase, the method further includes:

The extended service attributes are used to meet the different service requirements of the tenants, and at the same time, an extended column corresponding to the newly added service attribute is generated, and the extended column is only visible to the tenant.

Different tenants use the same initial business entity metadata extension to generate instances to share the same database table, and the columns corresponding to the initial business entity metadata are shared by all tenants; at the same time, add custom extensions for tenants according to the custom attributes of specific business entities generated by tenants Columns, custom extension columns are only visible by this tenant. After a tenant adds a custom column, only the tenant adds data to the column. Due to the sparse column storage feature of the Key-Value database, other tenants do not have the data in the tenant's custom column and do not occupy any extra space. At this time, the Key-Value database table CRM structure shared by tenant 1 business entity "student", tenant 2 business entity "employee" and tenant N business entity "administrator" is automatically expanded into table 6:

Table 6 Key-Value database table CRM structure extension table

Step 104, in the instance running phase, insert the tenant ID as the RowKey prefix into the business entity data of the Key-Value database, query the business entity data through the query range of the RowKey generated by the tenant ID, and start from the Key-Value within the query range. The business entity data is fetched from the Value database, and an interactive interface is generated according to the metadata of the specific business entity so as to display the business entity data.

The querying service entity data by generating the query range of the RowKey generated by the tenant ID specifically includes: querying the Key-Value database, setting the query range according to the tenant ID and the table name of the business entity, and setting Within the specified query scope, query and obtain the business entity data according to the query conditions set by the user.

In the instance running phase, insert the tenant ID as the RowKey prefix of all business entity data into the Key-Value database, generate the RowKey query scope through the tenant ID, and take out the business entity data from the Key-Value database, according to the customized specific business entity Metadata generation interface.

The generating the interactive interface according to the specific business entity metadata specifically includes:

Obtaining the specific business entity metadata of the tenant according to the identifier of the tenant;

generating query items according to the index column information and data types of the tenant's specific business entity metadata;

displaying query results according to display tags and business entity data in the tenant-specific business entity metadata;

The new item of the new page is generated according to the display label of the business entity, the attribute display label of the business entity, and the data type of the business entity in the metadata of the specific business entity of the tenant.

The inserting the business entity data into the Key-Value database with the tenant ID as the RowKey prefix specifically further includes: using the tenant ID + the table name of the business entity as the RowKey prefix of the business entity data.

Obtain the metadata of the business entity "student" through the tenant ID "Tenant001", and generate the content and style of the newly created or modified page through the business entity attribute display label and data type of the metadata. Fill in the complete user information, and insert the data into the Key-Value database. When inserting data, use "tenant ID + library table name" as the prefix of the data RowKey, such as "Tenant001CRMStudent001". Similarly, tenant 2 represents "Tenant002" to obtain the business entity "employee" to generate a new or modify page, and at the same time insert employee "Tenant002CRMEmployee001", the same is true for tenant N. At this time, the data in the CRM library table is shown in Table 7, where BASE represents the initial business metadata structure table, and CUSTOM represents the extended business metadata structure table:

Table 7 CRM database table data

RowKey List Tenant001CRMStudent001 BASE:USER_ID:Student001 Tenant001CRMStudent001 BASE: USER_NAME: Wang Xiaoer Tenant001CRMStudent001 BASE:USER_EMAIL:wangxe@stu.com Tenant001CRMStudent001 CUSTOM:STUDENT_LEVEL:1 Tenant002CRMEmployee001 BASE:USER_ID:Employee001 Tenant002CRMEmployee001 BASE: USER_NAME: Li Du Tenant002CRMEmployee001 BASE:USER_EMAIL:lid@company.com Tenant002CRMEmployee001 CUSTOM:DEPARTMENT:Development

When entering the query page, use the tenant 1 identifier "Tenant001" to get the metadata of the business entity "student", and get all the index items in the metadata to generate the query page. The index item display labels include "student name", "email", "grade" . The query result displays all attributes of the custom business entity, including "Student ID", "Student Name", "Email", and "Grade". Similarly, use the tenant 2 identifier "Tenant002" to obtain the metadata of the business entity "employee", and obtain all index items in the metadata to generate a query page. The index item display labels include "employee name", "email", and "department". The query result displays all attributes of the custom business entity, including "Employee ID", "Employee Name", "Email", and "Department". When querying the database table data of a certain tenant, set the query range according to the tenant ID and database table name, and within this range, query and obtain data according to the query conditions set by the user. Specifically, use "tenant ID + database table name" Set it to StartRow, set StartRow plus one to EndRow, all the data of the tenant in the database table is within this range, so that the query speed of the tenant is only related to the amount of data of the tenant itself, and not to other tenant data Quantity is irrelevant. In this case, when querying tenant 1 business entity "student" data, set StartRow to "Tenant001CRM" and EndRow to "Tenant 001CRN". After setting the range, query tenant 1 data only needs to match the query conditions within the range. Yes, without scanning the entire database table.

Specifically, in the instance running phase, when tenant 1's business requirements change, if it is necessary to add the attribute "professional" to the business entity "student", you only need to add the information of the attribute and the custom column name in the database template. , without any additional custom development or deployment. When the server capacity is insufficient due to the increase of operator tenants, it is only necessary to add servers for the distributed Key-Value database without additional data migration.

To sum up, the present invention proposes a multi-tenant extension method based on a key-value database. In the customization stage, the method expands business entities according to domain knowledge on the basis of initial metadata, and defines the display of business entities and their attributes. label to generate specific metadata that meets the different business needs of tenants; in the instance generation phase, a Key-Value database is created for the tenant based on the business entity metadata extended by the user; in the instance running phase, when the tenant inserts business data into the database, the " Tenant ID + library table name" is used as a prefix to generate business data RowKey, and an interactive interface is generated by obtaining tenant-specific business entity metadata, and business data is retrieved from the database and displayed by setting the query range through RowKey. The invention supports customized generation of applications that meet the individual needs of tenants, avoids repeated development for businesses with similar business processes, and uses a shared Key-Value database to facilitate expansion and reduce operating costs.

Professionals should further realize that the units and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the relationship between hardware and software Interchangeability. In the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the embodiments of the present invention.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

The specific implementation manners described above further describe the technical solutions and beneficial effects of the embodiments of the present invention in detail. It should be understood that the above descriptions are only specific implementation modes of the embodiments of the present invention and are not intended to limit Within the protection scope of the embodiments of the present invention, any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the embodiments of the present invention shall be included in the protection scope of the embodiments of the present invention.

Claims (2)

1. A multi-tenant extension method based on a key-value database, characterized in that the method comprises: Get initial business entity metadata; In the customization stage, business attributes are extended on the initial business entity metadata, business entities and display labels are defined for the business attributes, and specific business entity metadata meeting multi-tenant requirements are generated; In the instance generation phase, a key-value Key-Value database is created according to the metadata of the specific business entity; In the instance running phase, the business entity data is inserted into the Key-Value database with the tenant ID as the RowKey prefix, and the business entity data is queried within the query range of the RowKey generated by the tenant ID, and the Key-Value database is retrieved within the query range Take out the business entity data, and generate an interactive interface according to the specific business entity metadata, so as to display the business entity data; During the generating instance phase, the method further includes: All tenants share one Key-Value database, and the column corresponding to the initial business entity metadata is shared by all tenants; During the generating instance phase, the method further includes: The extended business attributes are used to meet the different business requirements of the tenants, and at the same time generate extended columns corresponding to the newly added business attributes, and the extended columns are only visible to the tenants; The querying service entity data by generating the query range of the RowKey generated by the tenant ID specifically includes: querying the Key-Value database, setting the query range according to the tenant ID and the table name of the business entity, and setting Within the specified query scope, query and obtain the business entity data according to the query conditions set by the user; The generating the interactive interface according to the specific business entity metadata specifically includes: Obtaining the specific business entity metadata of the tenant according to the identifier of the tenant; generating query items according to the index column information and data types of the tenant's specific business entity metadata; displaying query results according to display tags and business entity data in the tenant-specific business entity metadata; Generate a new item on the new page according to the display label of the business entity of the specific business entity metadata of the tenant, the attribute display label of the business entity, and the data type of the business entity; The business entity data inserted into the Key-Value database with the tenant ID as the RowKey prefix specifically further includes: using the tenant ID + the table name of the business entity as the RowKey prefix of the business entity data; In the customization phase, the tenant customizes the initial business entity metadata based on domain knowledge based on the initial business entity metadata, and generates tenant-specific business entity metadata by modifying the initial column information and adding custom column information. 2. The multi-tenant extension method based on key-value database according to claim 1, characterized in that, the metadata of the initial business entity and the metadata of the specific business entity at least include: the table name of the business entity, the business The display label of the entity, the attribute column name of the business entity, the data type of the business entity, the index column ID of the business entity, and the attribute display label of the business entity.